Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Packistryphp | Packistry | < 0.13.0 |
Related Weaknesses (CWE)
References
- https://github.com/packistry/packistry/commit/7740b48f0f4ecbe63099fb056c8a146180Patch
- https://github.com/packistry/packistry/pull/276Issue TrackingPatch
- https://github.com/packistry/packistry/security/advisories/GHSA-4r9m-jp53-vgmwPatchVendor Advisory
FAQ
What is CVE-2026-27968?
CVE-2026-27968 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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...
How severe is CVE-2026-27968?
CVE-2026-27968 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-27968?
Check the references section above for vendor advisories and patch information. Affected products include: Packistryphp Packistry.