'openssl dgst' one-shot codepath silently truncates inputs >16MB
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: OpenSSL OpenSSL 3.5.5, 3.6.1; azl3 openvmm 0.2.0-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to OpenSSL OpenSSL 3.5.5, 3.6.1; azl3 openvmm 0.2.0-1 on Azure Linux 3.0 Release Notes 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
Primary sources: NVD · CVE.org · FIRST EPSS
Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-shot signing algorithms and reports success instead of an error. Impact summary: A user signing or verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire file is authenticated while trailing data beyond 16MB remains unauthenticated. When the 'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit, the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what the documentation states. This creates an integrity gap where trailing bytes can be modified without detection if both signing and verification are performed using the same affected codepath. The issue affects only the command-line tool behavior. Verifiers that process the full message using library APIs will reject the signature, so the risk primarily affects workflows that both sign and verify with the affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are unaffected. The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are outside the OpenSSL FIPS module boundary. OpenSSL 3.5 and 3.6 are vulnerable to this issue. OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
- Published
- Jan 27, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-347
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl3.5.0 and later · before 3.5.5
- openssl openssl3.6.0 and later · before 3.6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 3.6.0 and later · before 3.6.1affected · semver
- 3.5.0 and later · before 3.5.5affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | openssl | before 1:3.5.1-7.el10_1.alma.1 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-devel | before 1:3.5.1-7.el10_1.alma.1 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-libs | before 1:3.5.1-7.el10_1.alma.1 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-perl | before 1:3.5.1-7.el10_1.alma.1 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:9 | openssl | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| AlmaLinux:9 | openssl-devel | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| AlmaLinux:9 | openssl-libs | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| AlmaLinux:9 | openssl-perl | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| Alpine:v3.22 | openssl | from 3.5.0 · before 3.5.5-r0 | 3.5.5-r0 |
| Debian:13 | openssl | before 3.5.4-1~deb13u2 | 3.5.4-1~deb13u2 |
| Debian:14 | openssl | before 3.5.5-1 | 3.5.5-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.5.1 | 3.5.0-160000.5.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.5.3-2.1 | 3.5.3-2.1 |
| Red Hat:enterprise_linux:10.1 | openssl | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-debuginfo | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-debugsource | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-devel | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-libs | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-libs-debuginfo | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | openssl-perl | before 1:3.5.1-7.el10_1 | 1:3.5.1-7.el10_1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.5.1-7.el9_7 | 1:3.5.1-7.el9_7 |
+12
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
Published before and after this one in the same product
- ← EarlierCVE-2025-11187Jan 27, 2026 · Improper validation of PBMAC1 parameters in PKCS#12 MAC verification26Monitor
- ← EarlierCVE-2025-15468Jan 27, 2026 · NULL dereference in SSL_CIPHER_find() function on unknown cipher ID23Monitor
- Later →CVE-2025-66199Jan 27, 2026 · TLS 1.3 CompressedCertificate excessive memory allocation23Monitor
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 |
|---|---|---|
| OpenSSL OpenSSL | 3.5.5 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.1 | Vendor (CNA) |
| azl3 openvmm 0.2.0-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:openssl | 1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| alpine:openssl | 3.5.5-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:openssl | 3.5.4-1~deb13u2 · Debian:13 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.3-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-config-fips | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-devel | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:openssl-perl | 1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| rocky linux:openssl | 1:3.5.1-7.el10_1 · Rocky Linux:10 | Package registry (OSV) |
| suse:openssl-3 | 3.5.0-160000.5.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Stanislav Fort (Aisle Research)reporter
- Viktor Dukhovniremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.