NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-22731 — spring-boot-starter-actua…

HIGH

CVE-2026-22731 is a high-severity (CVSS 8.2) CWE-288 vulnerability in org.springframework.boot:spring-boot-starter-actuator. A fix is available for org.springframework.boot:spring-boot-starter-actuator — see the affected versions and patch details below.

Authentication Bypass under Actuator Health groups paths

Also known asGHSA-8hfc-fq58-r658
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22731.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk+0.01%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.28%0.56%0.85%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.springframework.boot:spring-boot-starter-actuator☕org.springframework.boot:spring-boot-starter-actuator☕org.springframework.boot:spring-boot-starter-actuator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requires authentication is declared under a specific path, already configured for a Health Group additional path. This issue affects Spring Boot: from 4.0 before 4.0.3, from 3.5 before 3.5.11, from 3.4 before 3.4.15. This CVE is similar but not equivalent to CVE-2026-22733, as the conditions for exploit and vulnerable versions are different.

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.boot:spring-boot-starter-actuator≥ 3.4.0No fix
☕Mavenorg.springframework.boot:spring-boot-starter-actuator≥ 3.5.0&&< 3.5.123.5.12org.springframework.boot:spring-boot-starter-actuator:3.5.12
☕Mavenorg.springframework.boot:spring-boot-starter-actuator≥ 4.0.0-M1&&< 4.0.44.0.4org.springframework.boot:spring-boot-starter-actuator:4.0.4

Affected Products

1 product · 3 configurations
Application
spring bootvmware
≥ 4.0.0 && < 4.0.4
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-starter-actuator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2026-22731; check the affected-versions list above or the advisory for the patched release of org.springframework.boot:spring-boot-starter-actuator, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
To mitigate, ensure that application endpoints requiring authentication are not declared under paths already configured as Health Group additional paths within Spring Boot applications using Actuator. Review and adjust your application's configuration to prevent this overlap. A redeployment of the application is required for changes to take effect.
Source: Red Hat security advisory for CVE-2026-22731 (CC BY 4.0)
ProductFixed inAdvisory
AMQ Clients 2026.Q3spring-bootRHSA-2026:69459
HawtIO HawtIO 4.4.0spring-bootRHSA-2026:25089
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14spring-bootRHSA-2026:17668
Red Hat OpenShift Dev Spaces 3.27devspaces/openvsx-rhel9:1776716842RHSA-2026:10175

Frequently Asked Questions

Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requires authentication is declared under a specific path, already configured for a Health Group additional path. This issue affects Spring Boot: from 4.0 before 4.0.3, from 3.5 before 3.5.11, from 3.4 before 3.4.15. This CVE is similar but not equivalent to CVE-2026-22733, as the conditions for exploit and vulnerable versions are different.
O3 Security · Impact-Aware SCA

Is CVE-2026-22731 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-22731: spring-boot-starter — Fixed in 3.5.12