GitHub PAT written to debug artifacts
Published Jan 24, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
GitHub PAT written to debug artifacts
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
In some circumstances, debug artifacts uploaded by the CodeQL Action after a failed code scanning workflow run may contain the environment variables from the workflow run, including any secrets that were exposed as environment variables to the workflow. Users with read access to the repository would be able to access this artifact, containing any secrets from the environment.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- Security advisory ↗
- Source repository ↗
- Source repository ↗
- Patch commit ↗
- https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough ↗
- news.ycombinator.com ↗
- www.praetorian.com ↗
Record history
Published Jan 24, 2025 · Last refreshed Nov 3, 2026