CVE-2026-27968: Packistry is a self-hosted Composer repository designed to handle PHP package distribution

Q: How do I fix CVE-2026-27968?

packistry: upgrade to 0.13.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-27968 being exploited?

CVE-2026-27968 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-27968 affect?

CVE-2026-27968 affects packistry. Severity is medium (CVSS 4.3). 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 resu

Q: How urgent is CVE-2026-27968?

Priority 18/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-27968 is a medium-severity flaw (CVSS 4.3) affecting packistry. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 t

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-287, CWE-613
Published	2026-02-26
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: packistryphp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-26 02:16 UTCPublished CVE record published
2026-06-17 10:27 UTCUpdated Record last modified

packistryphp packistry UPGRADE

Affected: < 0.13.0

Fixed in: 0.13.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy packistry || rpm -q packistry || packistry --version

2. UPGRADE to 0.13.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade packistry

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade packistry

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-27968?

packistry: upgrade to 0.13.0. Exact commands for each OS are on this page.

Is CVE-2026-27968 being exploited?

CVE-2026-27968 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-27968 affect?

CVE-2026-27968 affects packistry. Severity is medium (CVSS 4.3). 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 resu

How urgent is CVE-2026-27968?

Priority 18/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

References

← Back to latest CVEs