Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconGain local admin or physical access to host
-
DeliveryGenerate attacker RSA key pair
-
ExploitSign malicious firmware, embed matching modulus
-
InstallFlash tampered firmware to PS3111-S11
-
C2Controller accepts forged signature
-
ExecuteMalicious firmware persists below OS
-
ImpactExfiltrate or tamper with drive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires the ability to issue firmware-update commands to the PS3111-S11 controller, which per CVSS PR:H and AV:L means local high-privilege access - host administrator/root or physical/debug (JTAG) access to the drive - not remote or network exploitation. The specific enabling weakness is that the controller reads the RSA public modulus from the firmware image's own signature segment rather than from immutable storage, so any attacker-supplied key pair with a self-consistent modulus/signature passes verification. Limiting factors: the attacker must already hold privileged local access to flash firmware, no default network-facing path exists, and exploitation is per-device rather than scalable across a fleet remotely; user interaction is not required once flash access is obtained. |
| Impact | This is a high-severity but access-gated issue. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N) indicates local access with high privileges is required - an attacker must already be able to issue vendor/firmware-update commands to the drive, typically implying local administrator/root on the host or physical/JTAG access, not remote unauthenticated exploitation. Weighed against that, the impact metrics are maximal (VC:H/VI:H/VA:H and subsequent-system SC:H/SI:H/SA:H), reflecting that malicious firmware sits below the operating system and can persist across OS reinstalls, exfiltrate or tamper with all data passing through the controller, and brick the device. A public POC exists, which raises practical risk, but there is no KEV listing and no EPSS score provided, and the high-privilege prerequisite means this is more a targeted/supply-chain and evil-maid concern than a mass-exploitation one. The realistic threat model is firmware implants, evil-maid attacks, and supply-chain tampering rather than opportunistic remote compromise; organizations handling sensitive data on affected drives should nonetheless treat firmware-level persistence as urgent given how hard it is to detect and remediate. |
| Exploit ScenarioDerived | An attacker with local admin on the host, or brief physical access to the machine (evil-maid), generates an RSA key pair, signs a malicious firmware image, embeds the matching modulus in the signature segment, and flashes it to the PS3111-S11 controller, which accepts it as valid. The implanted firmware persists beneath the OS across reinstalls and can silently exfiltrate or modify stored data. A public POC (the 'psychite' toolkit) demonstrates the signature-bypass, lowering the bar to weaponize this. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 31, 2026
Firmware signature verification bypass in Phison PS3111-S11 SATA SSD controller firmware allows an attacker to load arbitrary, attacker-signed firmware onto the drive. Because the controller validates RSA signatures against a public modulus stored inside the firmware image itself instead of an immutable hardware root of trust, an attacker can generate their own RSA key pair, sign malicious firmware, embed the matching modulus, and have the controller accept it as authentic. Publicly available exploit code exists (VulnCheck advisory and the 'psychite' toolkit); there is no public exploit identified as being used in active attacks at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis, and because the flaw is in how the trust root is anchored, a fix likely requires updated firmware or hardware that validates signatures against an immutable/OTP-stored key rather than a modulus carried in the image; monitor Phison and the downstream SSD vendor for firmware updates and confirm any fix independently before relying on it. Compensating controls: restrict local administrator/root on hosts to prevent unauthorized firmware-flash commands (trade-off: none significant, standard least-privilege); enforce full-disk encryption with keys held off the drive (e.g., host-based LUKS/BitLocker rather than relying on the SSD's own controller) so a malicious controller cannot silently read plaintext (trade-off: minor performance/management overhead); enforce physical security and tamper-evident controls to counter evil-maid/JTAG access (trade-off: operational only); and for high-assurance environments, avoid or retire drives built on this controller for sensitive workloads. Refer to the VulnCheck advisory for authoritative guidance.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Phison PS3111-S11 is a widely used DRAM-less SATA III controller found in budget consumer SSDs. Secure firmware update schemes are supposed to anchor their trust root - the public key/modulus used to verify signatures - in immutable, tamper-resistant storage (ROM, OTP fuses, or a hardware secure element) so that only firmware signed by the vendor's private key is accepted. This vulnerability is a textbook CWE-347 (Improper Verification of Cryptographic Signature) failure: the controller reads the RSA public modulus from a segment of the firmware image being verified, so the signature check reduces to 'does this image's signature validate against the key packaged in the same image?' - which any attacker-generated key pair satisfies. The cryptography (RSA) is not broken; the trust anchoring is, making the entire signature check security theater.
Know when Ps3111 S11 Controller Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Requires privileged local access to flash firmware (PR:H, AV:L); compromised controller firmware breaks out to affect the host/all stored data, so S:C with full C/I/A impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Phison PS3111-S11 controller firmware verifies RSA signatures using a public modulus embedded within the firmware image itself rather than anchored in immutable storage. Attackers can generate arbitrary RSA key pairs, sign modified firmware with the private key, embed the matching modulus in the signature segment, and the controller accepts the tampered firmware as valid.
Technical POC Analysis
The bug class is CWE-347, Improper Verification of Cryptographic Signature.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
The Phison PS3111-S11 SATA SSD controller contains a critical firmware signature bypass (CVE-2026-82876) enabling unauthorized firmware installation without vendor verification. Any organization using these controllers faces risk of persistent malware, data exfiltration, or encryption at the storage layer. No vendor patch exists, making hardware replacement the only remediation path.
No vendor-released patch identified at time of analysis. Interim mitigations include: disable automatic firmware updates; restrict physical and logical access to affected systems; implement storage-layer anomaly detection; prioritize hardware replacement with controllers offering cryptographic firmware validation via hardware root-of-trust; maintain forensic readiness for malware detection at firmware level.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-68462
GHSA-r5jx-v7f9-8wxc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB