CVE-2026-57897

CVE-2026-57897 exposes a gap that defenders have suspected but lacked CVE-documentation to act on: org-level Actions Run and Job APIs bridge repository boundaries in ways that contradict the security assumption that repo access controls provide the effective isolation boundary. If an actor with any org-level read access can enumerate job logs, step outputs, workflow metadata, or artifact references across all repos via these APIs, they bypass repo-scoped permissions entirely and gain a lateral movement and intelligence-gathering capability. The CVSS 6.5 and EPSS 0.003 scores are misleading for this vulnerability class. EPSS models opportunistic exploitation—script kiddies and automated scanners—but this is a primitive for targeted campaigns, not mass scanning. The actual threat model is 'any compromised or malicious insider with org-level API access,' which is far broader than the EPSS population implies. What these APIs expose matters more than the technical severity score suggests. Job names reveal service architectures. Step sequences expose deployment patterns. Artifact references map where the valuable data lives. Environment names and secret name references in workflow files enable precision targeting of follow-on attacks. One org-level credential compromise yields a complete architectural map rather than a single repo's secrets—this is strategic reconnaissance, not opportunistic theft. Audit which org-level roles currently have Actions API access. The default 'Read' org member role may qualify, and org administrators often underestimate what implicit read access these APIs grant. Check whether workflow_dispatch and workflow_run webhooks are also exposed at the org level. Review any third-party CI dashboards or GitHub-compatible tooling that may be surfacing these endpoints to broader audiences than intended. The deeper problem is structural, not configurable. The CI/CD tooling ecosystem has created organizational pressure that makes broad org-level Actions API access effectively mandatory—vendors build products that depend on this access, and defenders are making the only available choice when legitimate operational tooling requires it. Even if GitHub publishes a fix tomorrow, the remediation timeline for org-level trust model changes will be measured in years, and organizations that have operated under the implicit model have years of workflow metadata, job logs, and artifact references that an attacker with existing access may already possess. The vulnerability changes the liability posture, not necessarily the exploitability—the intelligence this API surfaces doesn't expire.

Reviewed through automated stages and approved by a human before publication.