CVE-2026-27968
- Source
- https://cve.org/CVERecord?id=CVE-2026-27968
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27968.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-27968
- Aliases
-
- GHSA-4r9m-jp53-vgmw
- Published
- 2026-02-26T01:57:12.752Z
- Modified
- 2026-03-03T02:56:51.997471Z
- Severity
-
- 4.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CVSS Calculator
- Summary
- Packistry accepts expired access tokens
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27968.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-287", "CWE-613" ] }- References
-
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27968.json
- https://github.com/packistry/packistry/commit/7740b48f0f4ecbe63099fb056c8a146180f8b283
- https://github.com/packistry/packistry/pull/276
- https://github.com/packistry/packistry/security/advisories/GHSA-4r9m-jp53-vgmw
- https://nvd.nist.gov/vuln/detail/CVE-2026-27968
Affected packages
Git / github.com/packistry/packistry
Affected ranges
- Type
- GIT
- Repo
- https://github.com/packistry/packistry
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed