s1
--:--:--UTC

Searching APEX

Starting…

  1. ○ Searching Threats, IOCs & Threat Intelligence locally
  2. ○ Querying external providers
  3. ○ Asking AI Forensic Validator
  4. ○ Creating new entry from validated hit

0s elapsed

CVE-2026-105770

📛 CVE Title

Octo STS discloses trust policy contents to unauthorized callers via Exchange error messages

Description

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.

Overview

State
PUBLISHED
Assigner (CNA)
chainguard
CVSS severity
MEDIUM
CVSS score
CVSS 5.3 / 10 5.3 5.3 / 10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Effective score
5.3 / 10 MEDIUM source: CNA overview
CWE(s)
CWE-209
Reserved
2026-10-05
Published
2026-11-03 00:41 UTC
Last updated
2026-11-03 00:41 UTC
Source
https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/105xxx/CVE-2026-105770.json

European Union Vulnerability Database ENISA EUVD

ENISA's official EU repository for curated vulnerability intelligence. Carries a separate identifier (EUVD-YYYY-NNNN) and frequently exposes an earlier-published description + CVSS than NVD does.

EUVD ID
EUVD-2026-115653

EUVD enrichment is queued; refresh the page in a few seconds.

Affected products (1)

VendorProductVersionsPlatforms
octo-sts app 0 (affected) —

Vendor references (3)

References embedded in the original CVE record by the assigning CNA.

Web references (0)

DuckDuckGo results ranked by threat-intel / vendor advisory domains. Generated by the 🔎 Find references (web) button above — same flow as the Remediations search.

No web references attached yet.

Remediations (10)

  • web:source.android.com

    This Section contains the available Android Security Bulletins, which provide fixes for possible issues affecting Android devices.

    2026-11-03 12:44 UTC
  • web:support.sap.com

    SAP security Patch Day Bulletin This post shares the information on security notes that remediate vulnerabilities discovered in SAP products. SAP strongly recommends that the customer visits the Support Portal and applies patches on priority to protect their SAP landscape. On 10th of February 2026 , SAP security patch day saw the release of 26 new security notes. Further, there was 1 update to ...

    2026-11-03 12:44 UTC
  • web:support.servicenow.com

    On October 29, 2026 , ServiceNow issued CVE - 2026 -103093, CVE - 2026 -103094, and CVE - 2026 -6877. Each of these security issues was identified through internal security testing, customer security assessments, or reports submitted through ServiceNow's responsible disclosure and bug bounty programs and was remediated independently. For security issues identified through responsible disclosure ...

    2026-11-03 12:44 UTC
  • web:www.aikido.dev

    Vulnerability remediation tools find security weaknesses in code and infrastructure and help teams fix them. Those weaknesses can come from a flaw in the code your team wrote, or a vulnerable open-source dependency, or a misconfigured server or cloud resource. The fix differs by origin. Fixing a vulnerability in a dependency usually means upgrading to a patched release, which fails when no ...

    2026-11-03 12:44 UTC
  • web:www.armorcode.com

    The Strategic Decision Matrix: When to Remediate vs. Mitigate Prioritization paralysis happens when everything looks urgent. Deciding between remediation and mitigation requires looking past the CVSS score and incorporating actual business context. The framework below walks through the same four factors covered in this section: exploitability, patch availability, asset criticality, and ...

    2026-11-03 12:44 UTC
  • web:www.beyondtrust.com

    Mitigation As of Oct 9, 2026 , a patch that remediates this vulnerability has been applied to all Remote Support SaaS customers. Self-hosted customers of Remote Support should manually apply the patch if their instance is not subscribed to automatic updates in their / appliance interface.

    2026-11-03 12:44 UTC
  • web:www.cve.org

    At cve .org, we provide the authoritative reference method for publicly known information-security vulnerabilities and exposures

    2026-11-03 12:44 UTC
  • web:www.oracle.com

    This Critical Patch Update contains 1448 new security patches across the product families listed below. Please note that a My Oracle Support (MOS) note summarizing the content of this Critical Patch Update and other Oracle Software Security Assurance activities is located at July 2026 Critical Patch Update: Executive Summary and Analysis.

    2026-11-03 12:44 UTC
  • web:www.oracle.com

    Prior Critical Patch Update and Critical Security Patch Update advisories should be reviewed for information regarding earlier published security patches. Refer to Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins for information about Oracle Security advisories.

    2026-11-03 12:44 UTC
  • web:www.secure.com

    Remediation fully removes a vulnerability by fixing its root cause — through a patch , code fix , or system replacement. Mitigation reduces the risk of exploitation without removing the flaw itself, using controls like network segmentation or access restrictions.

    2026-11-03 12:44 UTC

AI Forensic Analysis

Only Available for Registered Users. Sign in to view.

Raw JSON

The full cvelistV5 record. Download as CVE-2026-105770.json.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "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"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Utkarsh Baghel (hackerrexx)"
        }
      ],
      "datePublic": "2026-10-06T19:34:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Octo STS (<code>github.com/octo-sts/app</code>) before 0.11.2 returns trust policy configuration to callers whose OIDC token does not satisfy that policy. <code>TrustPolicy.CheckToken</code> included the policy's <code>issuer</code>, <code>subject</code> and <code>audience</code> values or patterns and <code>claim_pattern</code> names and regular expressions in its <code>PermissionDenied</code> errors, which <code>Exchange</code> returned verbatim. <code>Exchange</code> also selected the GitHub App installation before checking the token, so errors from resolving the policy's <code>app</code> or <code>app_pattern</code> 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 <code>owner/repo</code> 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."
            }
          ],
          "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'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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "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"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-209",
              "description": "CWE-209: Generation of Error Message Containing Sensitive Information",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-03T00:41:24.502Z",
        "orgId": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
        "shortName": "chainguard"
      },
      "references": [
        {
          "name": "GHSA-h5p6-j8m9-xx4p",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/octo-sts/app/security/advisories/GHSA-h5p6-j8m9-xx4p"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/octo-sts/app/commit/88c6432adc4f497ec69b574e1ce162a564a9e71a"
        },
        {
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/octo-sts/app/releases/tag/v0.11.2"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "<p>Upgrade to Octo STS 0.11.2 or later. The token is now checked against the trust policy immediately after the policy is loaded and before installation selection or app pin resolution. On a mismatch the detailed reason is logged and recorded on the operator audit event, and the caller receives only a generic &quot;PermissionDenied: token does not match trust policy&quot;. Policies that exist but cannot be read, parsed or compiled now return the same NotFound response as a missing policy. Users of the hosted service are protected once the fix is deployed.</p>"
            }
          ],
          "value": "Upgrade to Octo STS 0.11.2 or later. The token is now checked against the trust policy immediately after the policy is loaded and before installation selection or app pin resolution. On a mismatch the detailed reason is logged and recorded on the operator audit event, and the caller receives only a generic \"PermissionDenied: token does not match trust policy\". Policies that exist but cannot be read, parsed or compiled now return the same NotFound response as a missing policy. Users of the hosted service are protected once the fix is deployed."
        }
      ],
      "source": {
        "advisory": "GHSA-h5p6-j8m9-xx4p",
        "discovery": "EXTERNAL"
      },
      "title": "Octo STS discloses trust policy contents to unauthorized callers via Exchange error messages",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "<p>None for self-hosted deployments other than upgrading.</p>"
            }
          ],
          "value": "None for self-hosted deployments other than upgrading."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "82cea9a6-e9e3-46fe-bdb0-3673de380178",
    "assignerShortName": "chainguard",
    "cveId": "CVE-2026-105770",
    "datePublished": "2026-11-03T00:41:24.502Z",
    "dateReserved": "2026-10-05T19:21:04.930Z",
    "dateUpdated": "2026-11-03T00:41:24.502Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}