Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.33% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-22731High confidence
Authentication Bypass under Actuator Health groups paths
Spring · Spring Boot
8.2HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Spring Spring Boot and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.springframework.boot:spring-boot-starter-actuator | ECOSYSTEM: introduced 3.4.0; last affected 3.4.13 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-starter-actuator | ECOSYSTEM: introduced 3.5.0; fixed 3.5.12 | 3.5.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-starter-actuator | ECOSYSTEM: introduced 4.0.0-M1; fixed 4.0.4 | 4.0.4 | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.springframework.boot:spring-boot-starter-actuator | >= 3.4.0, <= 3.4.13 | Not stated | GitHub advisory ↗github reviewed aggregator · 16 Apr 2026 |
| mavenorg.springframework.boot:spring-boot-starter-actuator | >= 3.5.0, < 3.5.12 | 3.5.12 | GitHub advisory ↗github reviewed aggregator · 16 Apr 2026 |
| mavenorg.springframework.boot:spring-boot-starter-actuator | >= 4.0.0-M1, < 4.0.4 | 4.0.4 | GitHub advisory ↗github reviewed aggregator · 16 Apr 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-22731 · CSAF 2.0 · revision 3 · finalRed Hat Product SecuritySpring Boot: Spring Boot: Authentication bypass via misconfigured Health Group additional path
The vendor explicitly identifies these products as affected by this CVE.
- spring-boot as a component of Red Hat build of OptaPlanner 8
- spring-boot as a component of Red Hat Data Grid 8
- spring-boot as a component of Red Hat Fuse 7
- spring-boot as a component of Red Hat Single Sign-On 7
- Summary
- A flaw was found in Spring Boot. This vulnerability, an authentication bypass, occurs when an application endpoint requiring authentication is declared under a specific path already configured for a Health Group additional path. A remote attacker could exploit this to bypass authentication, potentially gaining unauthorized access to sensitive application endpoints. This could lead to information disclosure or unauthorized actions.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
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.
What
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.
Why
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.
What
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.
Why
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Authentication Bypass Using an Alternate Path or Channel → bypass an access boundary or take over an account
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-288 ↗
CWE-288: Authentication Bypass Using an Alternate Path or Channel. The product requires authentication, but the product has an alternate path or channel that does not require authentication.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Fixed
- AMQ Clients 2026.Q3
- HawtIO HawtIO 4.4.0
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:12650f16ec1d9a079736da2d7e7428c791ae9a105bc0237814b9a2edd9f9a0ae_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:b2ccfa151d86315f1973d9cbfb1d3564e9daea8e4eac04e6f7b9e06f4521fcde_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:bf8c28c1dbed78077a84baf2d43bb0119c37a088a480121395aefcceb89b066e_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:d0882e222cea223cd64110ecfdf6dfdbe4faa7526c31293d304367bf9bb6f16c_s390x as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:27e30c7cede8d846cac4c623e84c6791a64b918136c5b781e9e885139fe237fb_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e224aebfad7c18649dfba4361bc0a77e937da1e69c230efa25ea2f6e1f9b17c2_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e832fb5a60f8a5180462458de7f410d01d8423473c4501b1b2e64ee606cb19b5_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:fb7eb298c502721c2dc77cf25d073681b9e5a4d6a7f5b1107f70bb8f787d273d_s390x as a component of Red Hat OpenShift Dev Spaces 3.27
- Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
- Action
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Security Bulletin - July 21 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026Unable to load Security Bulletin - July 21 2026 Security Advisories & Bulletins November 2022: Atlassian Security Advisories Overview Archived Security Advisories Security Advisories for Apps July 2022: Atlassian Security Advisories Overview August 2022: Atlassian Security Advisories Overview January 2023: Securit
04
Evidence and provenance
Published 19 Mar 2026 · Last source change 20 Mar 2026, 15:33 UTC · CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-13345
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- spring-boot as a component of Red Hat AMQ Clients; spring-boot as a component of Red Hat build of OptaPlanner 8; spring-boot as a component of Red Hat Data Grid 8; spring-boot as a component of Red Hat Fuse 7; spring-boot as a component of Red Hat Single Sign-On 7 · Fixed: HawtIO HawtIO 4.4.0; registry.redhat.io/devspaces/openvsx-rhel9@sha256:12650f16ec1d9a079736da2d7e7428c791ae9a105bc0237814b9a2edd9f9a0ae_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:b2ccfa151d86315f1973d9cbfb1d3564e9daea8e4eac04e6f7b9e06f4521fcde_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:bf8c28c1dbed78077a84baf2d43bb0119c37a088a480121395aefcceb89b066e_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:d0882e222cea223cd64110ecfdf6dfdbe4faa7526c31293d304367bf9bb6f16c_s390x as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:27e30c7cede8d846cac4c623e84c6791a64b918136c5b781e9e885139fe237fb_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e224aebfad7c18649dfba4361bc0a77e937da1e69c230efa25ea2f6e1f9b17c2_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e832fb5a60f8a5180462458de7f410d01d8423473c4501b1b2e64ee606cb19b5_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:fb7eb298c502721c2dc77cf25d073681b9e5a4d6a7f5b1107f70bb8f787d273d_s390x as a component of Red Hat OpenShift Dev Spaces 3.27; Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
- After
- spring-boot as a component of Red Hat build of OptaPlanner 8; spring-boot as a component of Red Hat Data Grid 8; spring-boot as a component of Red Hat Fuse 7; spring-boot as a component of Red Hat Single Sign-On 7 · Fixed: AMQ Clients 2026.Q3; HawtIO HawtIO 4.4.0; registry.redhat.io/devspaces/openvsx-rhel9@sha256:12650f16ec1d9a079736da2d7e7428c791ae9a105bc0237814b9a2edd9f9a0ae_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:b2ccfa151d86315f1973d9cbfb1d3564e9daea8e4eac04e6f7b9e06f4521fcde_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:bf8c28c1dbed78077a84baf2d43bb0119c37a088a480121395aefcceb89b066e_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/openvsx-rhel9@sha256:d0882e222cea223cd64110ecfdf6dfdbe4faa7526c31293d304367bf9bb6f16c_s390x as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:27e30c7cede8d846cac4c623e84c6791a64b918136c5b781e9e885139fe237fb_amd64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e224aebfad7c18649dfba4361bc0a77e937da1e69c230efa25ea2f6e1f9b17c2_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:e832fb5a60f8a5180462458de7f410d01d8423473c4501b1b2e64ee606cb19b5_arm64 as a component of Red Hat OpenShift Dev Spaces 3.27; registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:fb7eb298c502721c2dc77cf25d073681b9e5a4d6a7f5b1107f70bb8f787d273d_s390x as a component of Red Hat OpenShift Dev Spaces 3.27; Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- 4.0 < 4.0.3; 3.5 < 3.5.11; 3.4 < 3.4.15 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 4.0 < 4.0.3; 3.5 < 3.5.11; 3.4 < 3.4.15 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.