How many CVEs have patched verifyAdjacentArchiveSignature?

1 published CVEs changed verifyAdjacentArchiveSignature in 0xJacky/nginx-ui, in 1 distinct patches totalling 11 changed lines, between 2026 and 2026.

What is the latest CVE that changed verifyAdjacentArchiveSignature?

CVE-2026-107812 (Nginx UI: Self-upgrade runs an unsigned binary verified only by a same-origin digest → RCE via a compromised mirror or MITM), published 2026-10-09, changed lines 346 to 356 of internal/upgrader/upgrade.go.

How does verifyAdjacentArchiveSignature compare to the rest of 0xJacky/nginx-ui?

0xJacky/nginx-ui has 15 CVEs with a located fix in total; 1 of them changed verifyAdjacentArchiveSignature.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

0xJacky/nginx-ui

Function

verifyAdjacentArchiveSignature

Name: verifyAdjacentArchiveSignature in 0xJacky/nginx-ui: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

internal/upgrader/upgrade.go

Last patched October 9, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

11

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

verifyAdjacentArchiveSignature in 0xJacky/nginx-ui was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 11 lines in total.

0xJacky/nginx-ui has 15 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed verifyAdjacentArchiveSignature, newest first, with the lines each fix touched.

Nginx UI: Self-upgrade runs an unsigned binary verified only by a same-origin digest → RCE via a compromised mirror or MITM
CVE-2026-107812 · lines 346–356 · +11 −0
High · CVSS 7.5
EPSS 0.2%2026-10-09

Get an alert when the next CVE fix lands in 0xJacky/nginx-ui, with the patched functions.

Monitor nginx-ui CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in 0xJacky/nginx-ui changed by the most CVE fixes.

Restore3 CVEs · internal/backup/restore.go loadManifest2 CVEs · internal/backup/manifest.go RestoreBackup2 CVEs · api/backup/restore.go verifyManifestSignatureWithFallback2 CVEs · internal/backup/manifest.go restoreNginxUIConfig2 CVEs · internal/backup/restore.go writeManifestFiles2 CVEs · internal/backup/manifest.go

All patched functions in 0xJacky/nginx-ui

Frequently asked questions

Common questions about CVE fixes to verifyAdjacentArchiveSignature.

How many CVEs have patched verifyAdjacentArchiveSignature?: 1 published CVEs changed verifyAdjacentArchiveSignature in 0xJacky/nginx-ui, in 1 distinct patches totalling 11 changed lines, between 2026 and 2026.
What is the latest CVE that changed verifyAdjacentArchiveSignature?: CVE-2026-107812 (Nginx UI: Self-upgrade runs an unsigned binary verified only by a same-origin digest → RCE via a compromised mirror or MITM), published 2026-10-09, changed lines 346 to 356 of internal/upgrader/upgrade.go.
How does verifyAdjacentArchiveSignature compare to the rest of 0xJacky/nginx-ui?: 0xJacky/nginx-ui has 15 CVEs with a located fix in total; 1 of them changed verifyAdjacentArchiveSignature.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track 0xJacky/nginx-ui CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing