{
  "id": "CVE-2026-101019",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-101019",
  "published_at": "2026-10-14T14:40:29.685Z",
  "title": "NGINX ngx_http_js_module vulnerability",
  "vendor": "F5",
  "product": "NGINX JavaScript",
  "cvss": {
    "score": 8.3,
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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\n\n Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.",
  "cwe": "CWE-436",
  "cvss_by_source": {
    "cna": 8.3
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "F5",
        "product": "NGINX JavaScript",
        "ranges": [
          "\u003e= 0.7.10, \u003c 1.0.2"
        ],
        "fixed_in": [
          "1.0.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade NGINX JavaScript to 1.0.2 or later."
    ],
    "workarounds": [
      "Applications processing signed XML should reject DTD-bearing input before calling xml.parse(). The check must cover the complete document after decoding its accepted input encoding; a parser-level DTD prohibition is preferable to a raw byte search for \"\u003c!DOCTYPE\". \n\nApplications should also treat absent security-relevant attributes as validation failures rather than optional values. nginx-saml deployments should explicitly validate Destination, request correlation when unsolicited SSO is not intended, assertion validity, bearer SubjectConfirmation, Recipient, and SubjectConfirmationData InResponseTo."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://my.f5.com/manage/s/article/K000162615"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
