GitHub token exposure via persisted checkout credentials
Published Apr 14, 2026 · Updated Apr 14, 2026
Credential exposure in PraisonAI before 4.5.140 allows remote attackers to obtain GitHub Actions tokens from uploaded artifacts. Affected workflows invoke actions/checkout without disabling credential persistence, leaving the token in .git/config when that file enters an artifact. Exploitation requires read access to such an artifact; the token permits only the repository actions assigned to the affected workflow.
Summary
What happened
Credential exposure in PraisonAI before 4.5.140 allows remote attackers to obtain GitHub Actions tokens from uploaded artifacts. Affected workflows invoke actions/checkout without disabling credential persistence, leaving the token in .git/config when that file enters an artifact. Exploitation requires read access to such an artifact; the token permits only the repository actions assigned to the affected workflow.
The record
- CVE
- CVE-2026-40313
- Published
- Apr 14, 2026
- Updated
- Apr 14, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI
- Classifications
- CWE-829, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.140
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo