Server-Side Request Forgery (SSRF) Affecting octo-sts package, versions <0.5.3-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-CHAINGUARDLATEST-OCTOSTS-10566844
- published30 Jun 2025
- disclosed26 Jun 2025
Introduced: 26 Jun 2025
NewCVE-2025-52477 (opens in a new tab)How to fix?
Upgrade Chainguard octo-sts to version 0.5.3-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream octo-sts package and not the octo-sts package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Octo-STS is a GitHub App that acts like a Security Token Service (STS) for the GitHub API. Octo-STS versions before v0.5.3 are vulnerable to unauthenticated SSRF by abusing fields in OpenID Connect tokens. Malicious tokens were shown to trigger internal network requests which could reflect error logs with sensitive information. Upgrade to v0.5.3 to resolve this issue. This version includes patch sets to sanitize input and redact logging.