CVE-2026-27968 Packistry accepts expired access tokens
Attackers can use expired deploy tokens to access repository endpoints, bypassing authentication controls in Packistry.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-27968?
CVE-2026-27968 is a medium-severity authentication bypass vulnerability in packistry, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-27968?
It affects 1 product.
Products include Packistryphp Packistry.
How do I fix CVE-2026-27968?
No fix has been published for CVE-2026-27968 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-27968 being exploited?
There is no known exploitation of CVE-2026-27968 in the wild and no public exploit code.
Sources
Also known as GHSA-4r9m-jp53-vgmw.