Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 02 Mar 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Packistryphp
Packistryphp packistry |
|
| CPEs | cpe:2.3:a:packistryphp:packistry:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Packistryphp
Packistryphp packistry |
Thu, 26 Feb 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 26 Feb 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Packistry
Packistry packistry |
|
| Vendors & Products |
Packistry
Packistry packistry |
Thu, 26 Feb 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Packistry accepts expired access tokens | |
| Weaknesses | CWE-287 CWE-613 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-26T14:53:10.334Z
Reserved: 2026-02-25T03:24:57.793Z
Link: CVE-2026-27968
Updated: 2026-02-26T14:53:05.300Z
Status : Analyzed
Published: 2026-02-26T02:16:23.990
Modified: 2026-03-02T18:04:44.283
Link: CVE-2026-27968
No data.
OpenCVE Enrichment
Updated: 2026-04-17T14:30:20Z