Encrypted PDF disclosure via brute-forceable cryptography
Published Apr 8, 2026 · Updated Apr 8, 2026
Cryptographic weakness in PDFium in Google Chrome before 147.0.7727.55 allows attackers to read encrypted PDF contents by brute force. Google has not published which PDFium cryptographic operation uses inadequate encryption strength; the linked Chromium issue remains access-restricted. Exploitation requires user interaction and affects confidentiality only, exposing protected document contents without altering data or interrupting Chrome.
Summary
What happened
Cryptographic weakness in PDFium in Google Chrome before 147.0.7727.55 allows attackers to read encrypted PDF contents by brute force. Google has not published which PDFium cryptographic operation uses inadequate encryption strength; the linked Chromium issue remains access-restricted. Exploitation requires user interaction and affects confidentiality only, exposing protected document contents without altering data or interrupting Chrome.
The record
- CVE
- CVE-2026-5889
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-326
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=147.0.7727.55 <147.0.7727.55
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo