Unauthorized access via published repository credentials
Published Oct 16, 2025 · Updated Oct 16, 2025
Hard-coded credentials associated with ATLAS-EPIC commit f29312c allow remote attackers to read and modify protected data. The referenced commit changes the Pages workflow from uploading the entire repository to uploading only the docs directory, so it appears to remove repository-wide exposure rather than introduce it. Public sources do not identify the credential file or protected service; network access is sufficient, without prior privileges or user interaction.
Summary
What happened
Hard-coded credentials associated with ATLAS-EPIC commit f29312c allow remote attackers to read and modify protected data. The referenced commit changes the Pages workflow from uploading the entire repository to uploading only the docs directory, so it appears to remove repository-wide exposure rather than introduce it. Public sources do not identify the credential file or protected service; network access is sufficient, without prior privileges or user interaction.
The record
- CVE
- CVE-2025-60639
- Published
- Oct 16, 2025
- Updated
- Oct 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 16, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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