CVE-2026-101019VulnerabilityPublished 14 Oct 2026Updated 28 Oct 2026

Libnginx mod js: Description NGINX JavaScript (njs) has a vulnerability where the njs XML module exposes entity-backed

Affects libnginx-mod-jsSource GCVE Database

Authoritative record:CVE-2026-101019· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 29 Oct 2026, 00:57 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10libnginx-mod-js`pkg:deb/ubuntu/libnginx-mod-js?arch=source&distro=stonking`Other threats	Affected 0.9.4-1build2 – 1.0.0-3 4 affected builds	Fixed in–
Ubuntu Pro 26.04 LTSlibnginx-mod-js`pkg:deb/ubuntu/libnginx-mod-js?arch=source&distro=esm-apps/resolute`Other threats	Affected 0.9.1-1ubuntu2 – 0.9.4-1ubuntu0.1~esm1 7 affected builds	Fixed in–
Ubuntu 24.04 LTSlibnginx-mod-js`pkg:deb/ubuntu/libnginx-mod-js?arch=source&distro=noble`Other threats	Affected =0.7.12-2 =0.8.2-1ubuntu1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users of nginx-saml with the built-in njs backend should consider additional validation controls or mitigations to detect replay or out-of-context responses.

Description

NGINX JavaScript (njs) contains a vulnerability in its XML module where entity-backed XML attributes are exposed inconsistently during canonicalization. This flaw allows an attacker to cause certain security-relevant attributes to appear missing or truncated while the XML signature verification still succeeds. In particular, deployments using nginx-saml with the built-in njs backend are affected, enabling bypass of expiry, destination, and request-correlation checks. The vulnerability does not allow signature or identity forgery and does not impact availability. It is a data plane issue without control plane exposure.

Impact

An unauthenticated attacker can manipulate signed XML attributes to appear absent or truncated, bypassing validation checks in affected consumers. In nginx-saml, this leads to bypassing expiry, destination, and request-correlation validations, enabling replay attacks or acceptance of responses outside their intended context. There is no impact on signature or identity integrity and no availability impact. The issue affects only the data plane with no control plane exposure.

Summary

The vulnerability in libnginx-mod-js's njs XML module arises from inconsistent handling of entity-backed XML attributes during canonicalization. Specifically, the $attr$Name getter may return undefined for attributes containing internal entity references, and the $attrs getter may only reflect the first attribute child. This inconsistency can be exploited by an unauthenticated attacker who obtains a legitimately signed XML document to bypass validation checks while still passing signature verification. Confirmed affected consumers include nginx-saml deployments using the built-in njs backend. The flaw allows bypassing of critical checks such as expiry, destination, and request correlation, potentially enabling replay attacks or acceptance of responses outside their intended context. The vulnerability does not permit forging signatures or identities and does not cause availability issues.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 00:57 UTC

Technical details

References

Community reviews

Related threats