Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-101019— NGINX ngx_http_js_module vulnerability

Quick assessment

Affected
F5 NGINX JavaScript
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

漏洞描述 NGINX JavaScript (njs) 存在一个安全漏洞，其中 njs 的 XML 模块在实体引用的 XML 属性处理上与 libxml2 的规范化（canonicalization）行为不一致。在 njs 的内置后端和 QuickJS 后端中，在规范化过程中， getter 可能会在属性明确存在且包含内部实体引用时返回 。此外， getter 可能仅返回第一个属性子节点派生的值。这可能导致未经身份认证的攻击者，在投入大量努力获取一份真正经过签名的文档后，能够跳过某些验证步骤，同时使签名验证仍成功通

CVSS 6.5 · Medium EPSS 0.20% · P9

Affected Version Matrix 1

VendorProduct Version RangeStatus
F5 NGINX JavaScript 0.7.10< 1.0.2 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-101019

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
NGINX ngx_http_js_module vulnerability
Source: CVE Program / CVE List V5
Vulnerability Description
Description NGINX JavaScript (njs) has a vulnerability where the njs XML module exposes entity-backed XML attributes inconsistently with libxml2 canonicalization. In both the built-in njs and QuickJS backends during the canonicalization process, the $attr$Name getter may return undefined for an explicitly present attribute containing an internal entity reference. The $attrs getter may return a value derived only from the first attribute child. This may allow an unauthenticated attacker that invests significant effort in obtaining a genuinely signed document to skip validation while signature verification succeeds. An nginx-saml deployment is a confirmed affected consumer when run with the built-in njs backend. Impact In affected signed-XML consumers, an unauthenticated attacker can cause security-relevant attributes to appear absent or truncated while signature verification succeeds. In nginx-saml, this can bypass expiry, Destination, and request-correlation checks, enabling replay or acceptance of a response outside its intended context. It does not permit signature or identity forgery, or a direct availability impact. There is no control plane exposure; this is a data plane issue only.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
解释冲突
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
F5 NGINX JavaScript 0.7.10 ~ 1.0.2 -

II. Public POCs for CVE-2026-101019

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-101019

请登录查看更多情报信息。

Other References for CVE-2026-101019 (1)

Same Patch Batch · F5 · 2026-10-14 · 11 CVEs total

CVE-2026-91184 8.8 HIGH NGINX Gateway Fabric vulnerability
CVE-2026-93479 8.1 HIGH NGINX map directive and regex matching vulnerability
CVE-2026-15176 8.1 HIGH NGINX ngx_http_core_module vulnerability
CVE-2026-97205 8.1 HIGH NGINX ngx_http_core_module vulnerability
CVE-2026-94197 7.5 HIGH NGINX Ingress Controller vulnerability
CVE-2026-104939 7.5 HIGH NGINX Ingress Controller vulnerability
CVE-2026-96615 6.5 MEDIUM NGINX Gateway Fabric vulnerability
CVE-2026-97629 6.5 MEDIUM NGINX ngx_http_ssl_module vulnerability
CVE-2026-95101 5.3 MEDIUM NGINX ngx_http_v3_module vulnerability
CVE-2026-101025 5.3 MEDIUM NGINX ngx_http_js_module vulnerability

IV. Related Vulnerabilities

Same product: NGINX JavaScript
Same vendor: F5
Same weakness: CWE-436

V. Comments for CVE-2026-101019

No comments yet

Leave a comment