Skip to main content
Menu
CVEs

PHP signature bypass in Phar archive verification

Affects PHP setups that verify OpenSSL-signed Phar archives against an installed public key. Fixed in PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13.

CVE-2026-128090EUVD-2026-130141Published November 19, 2026, updated

7.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
Who is exposed
Specific setups only

Summary

PHP's Phar extension can be tricked into accepting a modified, OpenSSL-signed Phar archive as valid, as long as the attacker can change the archive but not its public key file. An attacker can exploit this remotely, without logging in, though a user must take an action for the attack to work. An application that loads the altered archive may then run attacker-controlled PHP code.

Written by a model

Original description

PHAR OpenSSL signature bypass via algorithm downgrade.

The Phar extension selects the signature verification method from the signature type stored in the archive, and only the OpenSSL types consult the separate .pubkey file holding the trusted public key. An attacker who can modify an OpenSSL-signed Phar archive, but not its public key file, can switch the signature type to a keyless hash such as SHA-256 with a recomputed digest, so the altered archive passes verification even with phar.require_hash enabled. An application that loads the archive may then execute attacker-controlled PHP code. Native, tar-based and zip-based phars are affected.

This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.

Who should check

PHP teams loading OpenSSL-signed Phar archives with a .pubkey file, on PHP before 8.2.36, 8.3.37, 8.4.28 or 8.5.13, including native, tar and zip phars.

Not fixed by: Setting phar.require_hash alone does not fix it.

“Affected versions < 8.2.36 >= 8.3.0, < 8.3.37”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    The application relies on an OpenSSL-signed Phar with a public key installed through a trusted channel. The attacker can modify the archive but not its .pubkey public key file. The archive is a native, tar-based or zip-based executable phar. The application subsequently loads the archive.
  2. Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128090 (PHAR OpenSSL signature bypass via algorithm downgrade), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128090 (entry last updated 2026-11-20):
Affected:
- PHP Group PHP: fixed in 8.2.36; from 8.3.0, fixed in 8.3.37; from 8.4.0, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Conditions (all must be true for the bug to be hit):
- The application relies on an OpenSSL-signed Phar with a public key installed through a trusted channel. (source: https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr)
- The attacker can modify the archive but not its .pubkey public key file. (source: https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr)
- The archive is a native, tar-based or zip-based executable phar. (source: https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr)
- The application subsequently loads the archive. (source: https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-128090 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128090 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128090
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128090"}.

Affected versions

cve.now Index

38Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity8.7/10CVSS 7.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 88 if added to CISA KEV
  • Would score about 83 if CISA's SSVC rates exploitation active

Timeline

  1. cve.now early warning

    PHP readies critical updates to patch RCE flaw CVE-2026-115560

    1 day
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. CVE published
  4. First seen by cve.now
  5. Posted on X by cve.now1 day
  6. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/php-src · Advisory GHSA-68fq-fh7h-f8gr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128090
RecordNVD · CVE-2026-128090

Questions about CVE-2026-128090

Is CVE-2026-128090 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

PHP accepts an OpenSSL-signed Phar archive when the signature was downgraded to a weaker algorithm, so a modified archive can pass verification. Running the modified archive can then run attacker-controlled PHP code with the privileges of the affected process.

Source: github.com

Which versions are affected by CVE-2026-128090?

PHP: before 8.2.36; from 8.3.0 before 8.3.37; from 8.4.0 before 8.4.28; from 8.5.0 before 8.5.13.

Source: cve.now feed data

Am I affected, and how do I check?

PHP versions before 8.2.36, from 8.3.0 before 8.3.37, from 8.4.0 before 8.4.28, and from 8.5.0 before 8.5.13 are in the affected ranges. The issue applies only where the application relies on an OpenSSL-signed Phar with a public key installed through a trusted channel and then loads that archive; check the PHP version with the php -v command and whether the application uses Phar signature verification.

Source: github.com

How do I fix CVE-2026-128090?

Upgrade PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13, matching the release branch in use.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.