Vulnerability · Published Feb 26, 2026 · Assigned by GitHub_M

CVE-2026-27968Packistry accepts expired access tokens

Medium 4.3

In plain English

A medium-severity improper authentication in packistry from packistry. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities).

Severity (CVSS 3.1)4.3Medium

Exploit odds (30 days)0.2%top 88.1% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected products (as reported)

Vendor	Product	Versions
packistry	packistry	< 0.13.0

Weakness: CWE-287, CWE-613 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

https://github.com/packistry/packistry/security/advisories/GHSA-4r9m-jp53-vgmw x_refsource_CONFIRM
https://github.com/packistry/packistry/pull/276 x_refsource_MISC
https://github.com/packistry/packistry/commit/7740b48f0f4ecbe63099fb056c8a146180f8b283 x_refsource_MISC