Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-62242 – SSRF / Cloud Credential Exfiltration – Spring Boot Admin Server before 4.1.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62242 is a Server-Side Request Forgery (SSRF) vulnerability in Spring Boot Admin Server (by codecentric), affecting all versions before 4.1.2. Unauthenticated remote attackers can register malicious application instances with attacker-controlled healthUrl and managementUrl parameters, forcing the server to issue HTTP requests to arbitrary internal addresses — including cloud instance metadata services — and retrieve response bodies through the server’s built-in actuator proxy. With a CVSS v3.1 base score of 8.6 (HIGH), this vulnerability poses a critical risk to any internet-exposed Spring Boot Admin deployment, particularly in cloud-hosted environments where exploitation can result in the theft of IAM credentials and full cloud account compromise.

Technical details

  • Root cause: The instance registration endpoint (POST /instances) accepts healthUrl and managementUrl values without validating them against private IP ranges (RFC 1918, loopback, or link-local addresses) or cloud metadata endpoints. The internal Registration.checkUrl() method performs only basic syntactic validation (isAbsolute()), with no block list enforced for internal address space such as 169.254.0.0/16 or 10.0.0.0/8.
  • Trigger conditions: A single unauthenticated HTTP POST to the /instances endpoint is sufficient. No credentials, session token, API key, or user interaction are required.
  • Attack vector: An attacker submits a crafted instance registration payload with a malicious healthUrl (e.g., http://169.254.169.254/latest/meta-data/iam/security-credentials/) or managementUrl. The server’s StatusUpdater component automatically polls the registered healthUrl, and the InstancesProxyController proxies subsequent requests targeting /instances/{id}/actuator/** directly to the registered URL — returning the full response body to the attacker.
  • Impact: Exfiltration of HTTP responses from any internally reachable service, including AWS, GCP, and Azure instance metadata service tokens and IAM credentials. In cloud-hosted environments, successful exploitation can enable full cloud account takeover. The CVSS v4.0 vector reflects a High Subsequent System Confidentiality impact (SC:H), with no authentication barrier.

Affected software

  • Spring Boot Admin Server (de.codecentric:spring-boot-admin-server): all versions before 4.1.2

Severity

  • CVSS v3.1 Base Score: 8.6 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Spring Boot Admin Server to version 4.1.2 or later. This release introduces an SSRF check mechanism that validates registered URLs against private IP ranges and metadata endpoints prior to accepting instance registrations (fix commit 1f991ea, PR #5464).
  • If patching is not immediately possible:
    • Restrict access to the /instances registration endpoint via a firewall or reverse proxy, permitting only trusted internal source IPs.
    • Block outbound connections from the Spring Boot Admin Server host to link-local (169.254.0.0/16) and RFC 1918 address ranges at the network perimeter.
    • Do not expose Spring Boot Admin Server directly to the internet; place it behind authenticated access controls.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge