Internal data disclosure via unvalidated OIDC issuer
Published Jun 26, 2025 · Updated Jun 27, 2025
SSRF in Chainguard Octo STS before 0.5.3 allows remote attackers to reach internal services through crafted OIDC token issuer fields. The Exchange path extracts an unvalidated issuer from the bearer token and passes it to provider discovery, which follows attacker-chosen endpoints. No authentication or user interaction is required, and returned errors can expose sensitive response data from otherwise unreachable internal services.
Summary
What happened
SSRF in Chainguard Octo STS before 0.5.3 allows remote attackers to reach internal services through crafted OIDC token issuer fields. The Exchange path extracts an unvalidated issuer from the bearer token and passes it to provider discovery, which follows attacker-chosen endpoints. No authentication or user interaction is required, and returned errors can expose sensitive response data from otherwise unreachable internal services.
The record
- CVE
- CVE-2025-52477
- Published
- Jun 26, 2025
- Updated
- Jun 27, 2025
- Vendor
- Chainguard
- Product
- Octo STS
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2025CVE publishedPublication date reported by the CVE source.
- Jun 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo