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

> Attackers can use expired deploy tokens to access repository endpoints, bypassing authentication controls in Packistry.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-4r9m-jp53-vgmw

## What is CVE-2026-27968?

CVE-2026-27968 is a medium-severity authentication bypass vulnerability in packistry, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-27968?

It affects 1 product.


Products: Packistryphp Packistry.

## How do I fix CVE-2026-27968?

No fix has been published for CVE-2026-27968 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27968 being exploited?

There is no known exploitation of CVE-2026-27968 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27968 and fix it if it is affected.

What it is: CVE-2026-27968 is a medium-severity authentication bypass vulnerability in packistry, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27968 in the wild and no public exploit code.

Affected product: packistry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27968/ (Markdown: https://insights.sbomify.com/CVE-2026-27968/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27968
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27968
- OSV: https://osv.dev/vulnerability/CVE-2026-27968

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27968/
Summaries are generated and may contain mistakes; the official description above is the record.