CVE-2026-27968

Published: Feb 26, 2026Modified: Mar 2, 2026

4.3

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitability: 2.8 / Impact: 1.4

Source: security-advisories@github.com (Secondary)

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 (1)

Products: Packistryphp: Packistry

1 product

Configuration A

1 vulnerable

Vulnerable Software	Affected Versions
Packistryphp Packistry	Before 0.13.0

Related CWEs

Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Insufficient Session Expiration

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

References (3)

https://github.com/packistry/packistry/commit/7740b48f0f4ecbe63099fb056c8a146180f8b283

Source: security-advisories@github.com

Patch

https://github.com/packistry/packistry/pull/276

Source: security-advisories@github.com

Issue TrackingPatch

https://github.com/packistry/packistry/security/advisories/GHSA-4r9m-jp53-vgmw

Source: security-advisories@github.com

PatchVendor Advisory

Timeline

No history available yet.