High 2 vendors · 2 advisories

CVE-2026-84375: DoS (Denial of Service) js-yaml Dependency in Jira Software Data Center

CVE-2026-84375 key facts

CISA KEV: Not listed (catalogue checked Nov 10, 2026)
Highest advisory rating: High
CVSS base score: 7.5 (Atlassian), 7.5 (Red Hat)
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (Red Hat)
Weakness: CWE-835
Fixed releases: Atlassian: Jira Data Center and Server: 11.3.12 (LTS) recommended Data Center Only, Jira Data Center and Server: 10.3.26 (LTS) Data Center Only, Jira Service Management Data Center and Server: 11.3.12 (LTS) recommended Data Center Only, Jira Service Management Data Center and Server: 10.3.26 (LTS) Data Center Only
Red Hat: 3.15.2, 4.3.2, automation-platform-ui-0:2.6.14-1.el9ap, network-observability/network-observability-console-plugin-pf5-rhel9:1789978780, network-observability/network-observability-console-plugin-rhel9:1789978277, advanced-cluster-security/rhacs-main-rhel8:1789411269 and 44 more in the advisory
Vendor advisories: 2 from Atlassian, Red Hat
Listed by VulniPulse: Sep 2, 2026
Record changed: Nov 10, 2026

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

How do I fix CVE-2026-84375?

Upgrade to a fixed release named by the vendor:

Atlassian: Jira Data Center and Server: 11.3.12 (LTS) recommended Data Center Only, Jira Data Center and Server: 10.3.26 (LTS) Data Center Only, Jira Service Management Data Center and Server: 11.3.12 (LTS) recommended Data Center Only, Jira Service Management Data Center and Server: 10.3.26 (LTS) Data Center Only
Red Hat: 3.15.2, 4.3.2, automation-platform-ui-0:2.6.14-1.el9ap, network-observability/network-observability-console-plugin-pf5-rhel9:1789978780, network-observability/network-observability-console-plugin-rhel9:1789978277, advanced-cluster-security/rhacs-main-rhel8:1789411269

Upgrade to a fixed version listed by Atlassian: Jira Data Center and Server: 11.3.12 (LTS) recommended Data Center Only; Jira Data Center and Server: 10.3.26 (LTS) Data Center Only; Jira Service Management Data Center and Server: 11.3.12 (LTS) recommended Data Center Only; Jira Service Management Data Center and Server: 10.3.26 (LTS) Data Center Only. (Atlassian)

Vendor advisories for CVE-2026-84375

Atlassian

1 advisory

Advisory severityHigh7.5
High [CVE-2026-84375] DoS (Denial of Service) js-yaml Dependency in Jira Software Data Center
CVE-2026-84375Source published Oct 20, 2026
DoS (Denial of Service) js-yaml 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 October 20 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.11 (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.12 (LTS) recommended Data Center Only
Jira Data Center and Server: 10.3.26 (LTS) Data Center Only
Jira Service Management Data Center and Server: 11.3.12 (LTS) recommended Data Center Only
Jira Service Management Data Center and Server: 10.3.26 (LTS) Data Center Only
Mitigation guidance
Upgrade to a fixed version listed by Atlassian: Jira Data Center and Server: 11.3.12 (LTS) recommended Data Center Only; Jira Data Center and Server: 10.3.26 (LTS) Data Center Only; Jira Service Management Data Center and Server: 11.3.12 (LTS) recommended Data Center Only; Jira Service Management Data Center and Server: 10.3.26 (LTS) Data Center Only.
Full advisory and evidence Open source bulletin

Red Hat

1 advisory

Advisory severityHigh7.5
High [CVE-2026-84375] Denial of Service vulnerability in YAML parsing
CVE-2026-84375Source published Sep 1, 2026Source updated Sep 1, 2026
js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2 and 4.3.2, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in applications that parse untrusted YAML, and merge processing is enabled by default on these release lines. This issue is fixed in versions 3.15.2 and 4.3.2. An attacker can exploit this by providing a specially crafted YAML document that causes the parser to perform excessive processing when…
Affected products in this advisory
Red Hat Ansible Automation Platform 2.6 for RHEL 9
Network Observability (NETOBSERV) 1.12.3
Red Hat Advanced Cluster Security for Kubernetes 4.10
Red Hat Advanced Cluster Security for Kubernetes 4.11
53 more entries in the full advisory.
Source-reported affected versions
Affected-version details not available in this record.
Source-reported fixed versions
3.15.2
4.3.2
automation-platform-ui-0:2.6.14-1.el9ap
network-observability/network-observability-console-plugin-pf5-rhel9:1789978780
46 more entries in the full advisory.
Mitigation guidance
No mitigation guidance extracted; consult the source.
Full advisory and evidence Open source bulletin

References

CVE-2026-84375 recordCVE.org
CVE-2026-84375 detailNVD

All Atlassian advisories

Get an email when Atlassian publishes the next one.

See Atlassian's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Atlassian

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts on Android See app features