{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101019 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-101019 is a high-severity vulnerability in F5 NGINX JavaScript, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-101019 and fix it if it is affected.\n\nWhat it is: CVE-2026-101019 is a high-severity vulnerability in F5 NGINX JavaScript, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-101019 in the wild and no public exploit code.\n\nAffected product: F5 NGINX JavaScript. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-101019/ (Markdown: https://insights.sbomify.com/CVE-2026-101019/index.md)","id":"CVE-2026-101019","markdown":"https://insights.sbomify.com/CVE-2026-101019/index.md","name":"CVE-2026-101019","record":{"aliases":["AZL-108452","BELL-CVE-2026-101019","DEBIAN-CVE-2026-101019","GHSA-fvf3-54p5-jg2m","UBUNTU-CVE-2026-101019"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NGINX JavaScript module","requires_auth":"none","summary":"An unauthenticated attacker can bypass SAML security checks like expiry and destination validation by exploiting inconsistent XML attribute handling in NGINX JavaScript.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Description\nNGINX 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.\n\nImpact\nIn 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.\n\n Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NGINX ngx_http_js_module vulnerability","id":"CVE-2026-101019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in AssetView","id":"CVE-2026-101020"},"packages":[],"prev":{"headline":"dayrui XunruiCMS Group Editing Home.php group_all_edit sql injection","id":"CVE-2026-101018"},"products":["NGINX JavaScript"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["F5"]},"summary":"An unauthenticated attacker can bypass SAML security checks like expiry and destination validation by exploiting inconsistent XML attribute handling in NGINX JavaScript.","url":"https://insights.sbomify.com/CVE-2026-101019/"}