Live › vulnerability › CVE-2026-105770
Octo STS, a GitHub app that exchanges OIDC tokens for GitHub access, returned the issuer, subject, audience and claim rules of a trust policy in error messages to callers the policy does not trust. An attacker with any valid OIDC token, such as one from a repository they own, can read those matching rules, which often name internal repositories, branches, environments or cloud account identifiers, but cannot mint tokens or bypass the policy.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 01:47 UTC. All times on this page are UTC.
Teams that run their own Octo STS deployment before 0.11.2 and use trust policies that contain internal names or identifiers. Trust policies stored in private repositories are also readable through the flaw, so private storage does not protect them. Teams using only managed hosting, or running a version at or after 0.11.2, are not exposed.
No product ranges from the sources yet.
0.11.20.11.2 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Octo STS (github.com/octo-sts/app) before 0.11.2 returns trust policy configuration to callers whose OIDC token does not satisfy that policy. TrustPolicy.CheckToken included the policy's issuer, subject and audience values or patterns and claim_pattern names and regular expressions in its PermissionDenied errors, which Exchange returned verbatim. Exchange also selected the GitHub App installation before checking the token, so errors from resolving the policy's app or app_pattern pin were returned to callers the policy does not trust. An attacker who holds any validly signed OIDC token, such as a GitHub Actions token from a repository they own, and who knows or guesses a target owner/repo and identity name can read that policy's matching rules, even when the policy is stored in a private repository. These rules often name internal repositories, branches, environments or cloud account identifiers. The issue does not allow minting tokens or bypassing a trust policy. This issue is fixed in 0.11.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-105770")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.