CVE-2026-101019: CWE-436 Interpretation Conflict in F5 NGINX JavaScript
Description
NGINX JavaScript (njs) contains a vulnerability in its XML module where entity-backed XML attributes are inconsistently exposed during canonicalization. This inconsistency can cause certain XML attributes to appear missing or truncated while the XML signature verification still succeeds. This affects signed-XML consumers such as nginx-saml when using the built-in njs backend, potentially allowing replay attacks or acceptance of responses outside their intended context. The vulnerability does not allow signature forgery, identity spoofing, or direct denial of service. It is a data plane issue without control plane exposure.
CVSS v3.1
Score 6.5medium
Affected software
F5
NGINX JavaScript
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-101019 describes a vulnerability in NGINX JavaScript (njs) where the XML module's handling of entity-backed XML attributes conflicts with libxml2 canonicalization. Specifically, during canonicalization, 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 discrepancy can allow an unauthenticated attacker, who has obtained a legitimately signed document, to bypass validation checks while signature verification passes. The nginx-saml deployment using the built-in njs backend is a confirmed affected consumer. The vulnerability impacts security-relevant attributes such as expiry, Destination, and request-correlation checks, enabling replay or acceptance of responses outside their intended context.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to cause security-relevant XML attributes to appear absent or truncated during validation, while the signature verification still succeeds. In nginx-saml deployments using the built-in njs backend, this can bypass critical checks like expiry and request correlation, enabling replay attacks or acceptance of responses outside their intended context. There is no impact on signature or identity forgery, nor is there any direct availability impact. The issue affects only the data plane with no control plane exposure.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, users should be aware of the risk in signed-XML consumers using the built-in njs backend, such as nginx-saml, and consider mitigating controls at the application level if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- f5
- Date Reserved
- 2026-09-30T21:56:14.632Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acf966f2cdf04f6568bce05
Added to database: 10/14/2026, 14:49:19 UTC
Last enriched: 10/14/2026, 15:04:03 UTC
Last updated: 10/14/2026, 15:08:26 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.