CVE-2026-27099: Jenkins has a stored XSS vulnerability in node offline cause description

CVE-2026-27099 · Severity: low · CVSS 3.1 · Published 2026-02-18

Jenkins has a stored XSS vulnerability in node offline cause description

Technologies: org.jenkins-ci.main:jenkins-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-27099 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-27099 being exploited in the wild.
How severe is CVE-2026-27099?
Low severity, with a CVSS score of 3.1, published 18 February 2026.
Which products and versions are affected?
org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=2.542,fixed=2.551.
Is there a fix for CVE-2026-27099?
Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.551 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-27099?
Check whether you run org.jenkins-ci.main:jenkins-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.551 or later
    # set org.jenkins-ci.main:jenkins-core to 2.551 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=2.542,fixed=2.551

Identifiers

  • CVE-2026-27099
  • GHSA-85h6-5m3v-gx37

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.