CVE-2026-15343 GitHub CVE debrief

Who should care

GitHub Enterprise Server administrators and users who manage repositories with GitHub Actions workflows should be aware of this vulnerability and take steps to ensure their systems are updated to a fixed version. Additionally, security teams and vulnerability management teams should review the affected scope and severity to prioritize remediation efforts.

Technical summary

The vulnerability is caused by a path traversal issue in GitHub Enterprise Server, which allows an attacker to control the effective path through the dependency file's directory and symlink target. This can lead to the execution of injected workflows with access to repository secrets. The vulnerability affects all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.3, 3.20.5, 3.19.9, 3.18.12, and 3.17.18. It is essential to update to a fixed version to prevent exploitation.

Defensive priority

High

Recommended defensive actions

• Update GitHub Enterprise Server to a fixed version (3.21.3, 3.20.5, 3.19.9, 3.18.12, or 3.17.18)
• Review and restrict access to GitHub Actions workflows
• Monitor repository activity for suspicious workflow executions
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record was published on 2026-07-17T16:17:13.917Z and last modified on 2026-07-17T18:11:59.263Z. The NVD entry is currently Deferred. This information is based on the provided source corpus. Further verification is recommended to ensure accuracy.

Official resources