CVE-2026-62242: Spring Boot Admin Server < 4.1.2 SSRF via Unauthenticated Instance Registration
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Spring Boot Admin Server before 4.1.2 contains a server-side request forgery vulnerability that allows unauthenticated attackers to register instances with attacker-controlled healthUrl and managementUrl parameters without validation against private IP ranges or metadata endpoints. Attackers can force the server to make HTTP requests to arbitrary internal addresses and retrieve response bodies via the actuator proxy to exfiltrate cloud credentials.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-07-13).
Weakness: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality none, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-43556, GHSA-j4h2-3wwr-928r
VEDAS cluster: VEDAS:CRYSTALSQUID
Exploit Observer links 5 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (5)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2026/CVE-2026-62242.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2026/CVE-2026-62242.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-62242.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-62242.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-62242.rules
Vulnerability databases and vendor advisories (3)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-43556
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-j4h2-3wwr-928r
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-62242
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.989
strong exploit evidence - On CISA KEV
- Not listed
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| codecentric spring-boot-admin | before 4.1.2 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 4.1.2.
Vendor guidance:
- spring-boot-admin 4.1.2 Release Notes (release-notes, patch)
- Pull Request (issue-tracking, patch)
- Patch Commit (patch)
How to detect it
Nuclei template (active check)
Spring Boot Admin - Server-Side Request Forgery via Instance Registration
Spring Boot Admin Server before 4.1.2 allows unauthenticated attackers to register monitored instances with attacker-controlled healthUrl and managementUrl values through POST /instances without validating them against private IP ranges or metadata endpoints. The server then issues HTTP requests to these URLs while polling instance status, enabling server-side request forgery against internal addresses.
Name and description quoted from the template, written by VEDAS.
The template sends 1 request (POST /instances); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-62242.yamlShow the template (39 lines)
id: CVE-2026-62242
info:
name: "Spring Boot Admin - Server-Side Request Forgery via Instance Registration"
author: vedas-arpsyndicate
severity: high
description: |
Spring Boot Admin Server before 4.1.2 allows unauthenticated attackers to register
monitored instances with attacker-controlled healthUrl and managementUrl values through
POST /instances without validating them against private IP ranges or metadata endpoints.
The server then issues HTTP requests to these URLs while polling instance status,
enabling server-side request forgery against internal addresses.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-62242&match=exact
- https://subdomain.center/?engine=ammonites&keyword=spring-boot-admin&match=exact
classification:
cvss-metrics: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
cvss-score: 6.9
cve-id: CVE-2026-62242
cwe-id: CWE-918
metadata:
verified: false
max-request: 1
tags: cve,cve2026,spring-boot-admin,spring,ssrf,oast
http:
- raw:
- |
POST /instances HTTP/1.1
Host: {{Hostname}}
Content-Type: application/json
{"name":"vedas","healthUrl":"http://{{interactsh-url}}/health","managementUrl":"http://{{interactsh-url}}/actuator","serviceUrl":"http://{{interactsh-url}}/"}
matchers-condition: and
matchers:
- type: word
part: interactsh_protocol
words:
- "http"
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-62242 Spring Boot Admin - Server-Side Request Forgery. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-62242 Spring Boot Admin - Server-Side Request Forgery"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/instances"; nocase; fast_pattern; http.request_body; content:"healthUrl"; nocase; content:"://"; distance:0; classtype:web-application-attack; reference:cve,CVE-2026-62242; reference:url,https://www.exploit.observer/?keyword=CVE-2026-62242&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=spring-boot-admin&match=exact; sid:1072202; rev:1;)
CVE-2026-62242.rules on GitHub
References
Vendor advisories and patches
- spring-boot-admin 4.1.2 Release Notes (release-notes, patch)
- Pull Request (issue-tracking, patch)
- Patch Commit (patch)
Exploits and technical analysis
- Researcher Disclosure (technical-description, exploit, issue-tracking)
- https://www.vulncheck.com/advisories/spring-boot-admin-server-ssrf-via-unauthenticated-instance-registration (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.