CVE-2026-27968 json
Packistry accepts expired access tokens
published 2026-02-26 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8820
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
Packistry is a self-hosted Composer repository designed to handle PHP package distribution. Prior to version 0.13.0, RepositoryAwareController::authorize() verified token presence and ability, but did not enforce token expiration. As a result, an expired deploy token with the correct ability could still access repository endpoints (e.g., Composer metadata/download APIs). The fix in version 0.13.0 adds an explicit expiration check, and tests now test expired deploy tokens to ensure they are rejected.
Patch / fix
- packistryphp packistry 0.13.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- packistry packistry
Classification
References
-
github.com
/packistry/packistry/pull/276
issue-tracking, patch
-
github.com
/packistry/packistry/commit/7740b48f0f4ecbe63099fb056c8a146180f8b283
patch
-
github.com
/packistry/packistry/security/advisories/GHSA-4r9m-jp53-vgmw
patch, vendor-advisory
Sources
- CVE List CVE-2026-27968
- NVD CVE-2026-27968
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.