FKIE_CVE-2026-105770

Vulnerability from fkie_nvd - Published: 2026-11-03 01:16 - Updated: 2026-11-03 16:30
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Summary
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.
References
82cea9a6-e9e3-46fe-bdb0-3673de380178https://github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a
82cea9a6-e9e3-46fe-bdb0-3673de380178https://github.com/octo-sts/app/releases/tag/v0.11.2
82cea9a6-e9e3-46fe-bdb0-3673de380178https://github.com/octo-sts/app/security/advisories/GHSA-h5p6-j8m9-xx4p
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://pkg.go.dev",
          "defaultStatus": "unaffected",
          "packageName": "github.com/octo-sts/app",
          "product": "app",
          "programFiles": [
            "pkg/octosts/octosts.go",
            "pkg/octosts/trust_policy.go"
          ],
          "programRoutines": [
            {
              "name": "TrustPolicy.CheckToken"
            },
            {
              "name": "Exchange"
            }
          ],
          "repo": "https://github.com/octo-sts/app",
          "vendor": "octo-sts",
          "versions": [
            {
              "lessThan": "0.11.2",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s 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\u0027s 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\u0027s 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."
    }
  ],
  "id": "CVE-2026-105770",
  "lastModified": "2026-11-03T16:30:49.290",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-11-03T01:16:44.147",
  "references": [
    {
      "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
      "url": "https://github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a"
    },
    {
      "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
      "url": "https://github.com/octo-sts/app/releases/tag/v0.11.2"
    },
    {
      "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
      "url": "https://github.com/octo-sts/app/security/advisories/GHSA-h5p6-j8m9-xx4p"
    }
  ],
  "sourceIdentifier": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-209"
        }
      ],
      "source": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.