HighCVE-2026-107810

0xJacky Nginx-ui: Link Following (CVE-2026-107810)

Published 09.10.2026Last modified 20.10.2026Sources: BSI, CVE.org, OSV, Hersteller

Public exploit

What is affected, what to do

An exploit is publicly available. Update nginx_ui to version 2.5.0, nginx-ui to version 2.5.0, github.com/0xjacky/nginx-ui to version 1.9.10-0.20260728074146-a467ed652591.

Affected: 0xJacky Nginx-ui gte 2.0.0, < 2.5.0..*

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

8.1

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: Vendor (CNA), CVSS v3

8.1

CVSS v3

Severity High on the scale from 0 to 10.

Source: BSI, CVE.org, OSV, Hersteller

0.4 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 38.7

Show all metrics

Severity: High
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 82.47 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: PoC (publicly reported)
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 8.1 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 8.1
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.4 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 38.7; High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 09.10.2026
CISA assessment (SSVC): Exploitation: proof of concept · not automatable · Technical impact: partial; Source: CISA Vulnrichment, as of 13 October 2026
CWE CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect. Read in glossary: CWE-59, CWE-61

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, internal/backup/restore.go extracts inner archives before applying the restore_nginx and restore_nginx_ui flags and permits symlinks targeting the live Nginx configuration path. An authenticated user who can create and restore backups can craft a valid backup that places a symlink in the staging tree and then writes a regular file through that link, even when both restore flags are false. This can persistently inject configuration or cause denial of service when the modified files are later consumed. This issue is fixed in version 2.5.0.

Source: BSI CSAF, BSI WID Portal, NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, GitHub Security Advisories

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
0xJacky	nginx-ui	`≥ 2.0.0, < 2.5.0`	—
nginxui	nginx_ui	`2.0.0 – < 2.5.0`	`2.5.0`
Open Source	nginx-ui	`< 2.5.0`	`2.5.0`
go	github.com/0xjacky/nginx-ui	`1.9.10-0.20250517140552-daee3ac7ade1`	`1.9.10-0.20260728074146-a467ed652591`

Vendors and products

Weakness classes (CWE)

CWE-59Improper Link Resolution Before File Access ('Link Following')
Base
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Entry at MITRE CWE-59
CWE-61UNIX Symbolic Link (Symlink) Following
Compound
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
Entry at MITRE CWE-61

Public exploit references

Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

Public exploit references

Reference tagged as exploit	github.com (opens in a new tab)	PoC (publicly reported)reported, not verified	—

References & sources

github.com0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7x_refsource_CONFIRM, web, advisory, Exploit, Vendor advisory
github.com0xJacky/nginx-ui/commit/a467ed652591fc0cd1b466a1ec751b493faef9f7x_refsource_MISC, web, Patch
github.com0xJacky/nginx-ui/releases/tag/v2.5.0x_refsource_MISC, web, Release notes
github.com0xJacky/nginx-uipackage

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

20.10.2026Initial analysis by NVDNVD

Newly listed as affected:

Nginxui Nginx UI (2.0.0 – before 2.5.0)

New references:

Show 5 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Product configuration	added	—	OR cpe:2.3:a:nginxui:nginx_ui::::::::* versions from (including) 2.0.0 up to (excluding) 2.5.0
Reference type	added	—	GitHub, Inc.: https://github.com/0xJacky/nginx-ui/commit/a467ed652591fc0cd1b466a1ec751b493faef9f7 Types: Patch
Reference type	added	—	GitHub, Inc.: https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0 Types: Release Notes
Reference type	added	—	CISA-ADP: https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7 Types: Exploit, Vendor Advisory
Reference type	added	—	GitHub, Inc.: https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7 Types: Exploit, Vendor Advisory

Source identifier: nvd@nist.gov

13.10.2026Record modifiedCISA ADP

CISA assessment (SSVC): exploitation: proof of concept, automatable: no

New references:

https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7

Show 2 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Reference	added	—	https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7
SSVC assessment	added	—	{"id":"CVE-2026-107810","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-13T16:56:11.014444Z"}

Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

09.10.2026ReceivedGitHub

CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Weakness type: CWE-59, CWE-61

Description added or changed

New references:

Show 8 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, internal/backup/restore.go extracts inner archives before applying the restore_nginx and restore_nginx_ui flags and permits symlinks targeting the live Nginx configuration path. An authenticated user who can create and restore backups can craft a valid backup that places a symlink in the staging tree and then writes a regular file through that link, even when both restore flags are false. This can persistently inject configuration or cause denial of service when the modified files are later consumed. This issue is fixed in version 2.5.0.
CVSS	added	—	AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Weakness type (CWE)	added	—	CWE-59
Weakness type (CWE)	added	—	CWE-61
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/107xxx/CVE-2026-107810.json">CVE-2026-107810</a>
Reference	added	—	https://github.com/0xJacky/nginx-ui/commit/a467ed652591fc0cd1b466a1ec751b493faef9f7
Reference	added	—	https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0
Reference	added	—	https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7

Source identifier: security-advisories@github.com

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-107810"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-107810.svg?lang=en" alt="CVE-2026-107810 – NEOSEC Intel" height="20"></a>