CVE-2026-128090: PHAR OpenSSL signature bypass via algorithm downgrade
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: PHP Group PHP 8.2.36, 8.3.37, 8.4.28.
Low priority for now. Upgrade to PHP Group PHP 8.2.36, 8.3.37, 8.4.28 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
- Published
- Nov 19, 2026
- Updated
- Nov 19, 2026
- EPSS
- —
- CWE
- CWE-347
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · php
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Using php? Add it to your stack and be the first to know about CVEs like this one. (PHP)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (php). Independent of NVD's CPE analysis and usually ahead of it.
PHP Group PHP
- 8.2.0 and later · before 8.2.36affected · semver
- 8.3.0 and later · before 8.3.37affected · semver
- 8.4.0 and later · before 8.4.28affected · semver
- 8.5.0 and later · before 8.5.13affected · semver
Same product
php group: all recordsOther highest-scoring records for the same primary product.
- CVE-2006-3016Unspecified vulnerability in session.c in PHP before 5.1.3 has unknown impact and attack vectors, related to "certain characters in session…38Monitor
- CVE-2024-2756__Host-/__Secure- cookie bypass due to partial CVE-2022-31629 fix37Monitor
- CVE-2026-129496Timezone cache use-after-free can lead to remote code execution36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-127960Nov 19, 2026 · Denial of service through folded HTTP response headers34Monitor
- ← EarlierCVE-2026-128064Nov 19, 2026 · Mixed-case HTTPS and FTPS URLs can expose data in plaintext32Monitor
- Later →CVE-2026-129182Nov 19, 2026 · Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PHP Group PHP | 8.2.36 | Vendor (CNA) |
| PHP Group PHP | 8.3.37 | Vendor (CNA) |
| PHP Group PHP | 8.4.28 | Vendor (CNA) |
| PHP Group PHP | 8.5.13 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 19, 2026same day
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Ilia Alshanetskyreporter
- Alexandre Dauboisremediation developer
- Jakub Zelenkaremediation reviewer
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.