Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-16221: fast-uri vulnerable to host confusion via literal backslash authority delimiter

CVE-2026-16221 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
7.5 (Atlassian)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · base score 7.5, scored by openjsAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-436: Interpretation Conflict
EPSS
0.44% chance of exploitation in the next 30 days (38th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Fixed releases
  • Atlassian: Jira Data Center and Server: 11.3.11 (LTS) recommended Data Center Only, Jira Data Center and Server: 10.3.25 (LTS) Data Center Only, Jira Service Management Data Center and Server: 11.3.11 (LTS) recommended Data Center Only, Jira Service Management Data Center and Server: 10.3.25 (LTS) Data Center Only
Vendor advisories
2 from Atlassian, Splunk
Assigned by
openjs (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-16221; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2) do not treat a literal backslash character (U+005C) as an authority delimiter. Node's native WHATWG URL parser, used by fetch, undici, and Node's http and https clients, normalizes the backslash to a forward slash for special schemes such as http, https, ws, wss, ftp, and file. As a result, the two parsers extract different hosts from the same input string. Applications that use fast-uri to enforce host-based policy such as allowlists, denylists, loopback or SSRF filtering, redirect validation, or outbound proxy routing before passing the same URL into Node's URL or fetch consumers can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts. Patches: upgrade to fast-uri 4.1.1, 3.1.4, or 2.4.3. Workarounds: none.

Text from the CVE.org record (openjs).

How do I fix CVE-2026-16221?

Upgrade to a fixed release named by the vendor:

  • Atlassian: Jira Data Center and Server: 11.3.11 (LTS) recommended Data Center Only, Jira Data Center and Server: 10.3.25 (LTS) Data Center Only, Jira Service Management Data Center and Server: 11.3.11 (LTS) recommended Data Center Only, Jira Service Management Data Center and Server: 10.3.25 (LTS) Data Center Only
  • Upgrade to a fixed version listed by Atlassian: Jira Data Center and Server: 11.3.11 (LTS) recommended Data Center Only; Jira Data Center and Server: 10.3.25 (LTS) Data Center Only; Jira Service Management Data Center and Server: 11.3.11 (LTS) recommended Data Center Only; Jira Service Management Data Center and Server: 10.3.25 (LTS) Data Center Only. (Atlassian)

Vendor advisories for CVE-2026-16221

Atlassian

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-16221] Injection fast-uri Dependency in Jira Software Data Center

    CVE-2026-16221Source published

    Injection fast-uri Dependency in Jira Software Data Center. Affected: Jira Data Center and Server, Jira Service Management Data Center and Server. Listed in Atlassian's Security Bulletin of September 15 2026.

    Affected products in this advisory
    • Jira Data Center and Server
    • Jira Service Management Data Center and Server
    Source-reported affected versions
    • Jira Data Center and Server: 11.3.0 to 11.3.10 (LTS)
    • Jira Data Center and Server: 11.2.0 to 11.2.1
    • Jira Data Center and Server: 11.1.0 to 11.1.1
    • Jira Data Center and Server: 11.0.0 to 11.0.1

    12 more entries in the full advisory.

    Source-reported fixed versions
    • Jira Data Center and Server: 11.3.11 (LTS) recommended Data Center Only
    • Jira Data Center and Server: 10.3.25 (LTS) Data Center Only
    • Jira Service Management Data Center and Server: 11.3.11 (LTS) recommended Data Center Only
    • Jira Service Management Data Center and Server: 10.3.25 (LTS) Data Center Only
    Mitigation guidance
    • Upgrade to a fixed version listed by Atlassian: Jira Data Center and Server: 11.3.11 (LTS) recommended Data Center Only; Jira Data Center and Server: 10.3.25 (LTS) Data Center Only; Jira Service Management Data Center and Server: 11.3.11 (LTS) recommended Data Center Only; Jira Service Management Data Center and Server: 10.3.25 (LTS) Data Center Only.

Splunk

1 advisory
  • Advisory severityCritical

    Critical [CVE-2022-40897 +57] Third-Party Package Updates in Splunk SOAR - November 2026

    SVD-2026-1109Source published

    This bulletin covers 58 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk SOAR version 8.8.0, and higher. Affected product named by the advisory: Splunk SOAR 8.8.

    Affected products in this advisory
    • Splunk SOAR 8.8
    Source-reported affected versions
    • Splunk SOAR Below 8.8.0
    Source-reported fixed versions
    • Splunk SOAR 8.8.0
    Mitigation guidance
    • Upgrade Splunk SOAR to version 8.8.0, or higher.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All Atlassian advisories

Get an email when Atlassian publishes the next one.

See Atlassian's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Atlassian