Private repository access via expired deploy tokens
Published Feb 26, 2026 · Updated Feb 26, 2026
Improper authentication in Packistry before 0.13.0 allows remote authenticated users to read private repository content with expired tokens. RepositoryAwareController::authorize() checks token presence and ability but fails to call isExpired() before authorizing repository requests. Possession of an expired deploy token with the required repository-read ability is necessary, and exposure is limited to content that token could access.
Summary
What happened
Improper authentication in Packistry before 0.13.0 allows remote authenticated users to read private repository content with expired tokens. RepositoryAwareController::authorize() checks token presence and ability but fails to call isExpired() before authorizing repository requests. Possession of an expired deploy token with the required repository-read ability is necessary, and exposure is limited to content that token could access.
The record
- CVE
- CVE-2026-27968
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Packistry
- Product
- Packistry
- Classifications
- CWE-287, CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=< 0.13.0
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