- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.1, 4.0.4, 3.5.10
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.
Summary
Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled can make OpenSSL consume excessive CPU time, with the cost growing with the square of the message size. The description does not say how an attacker delivers such a message.
Original description
Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.
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-121482 (Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with…), 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-121482 (entry last updated 2026-11-18):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10
Fixed versions: 4.1.1, 4.0.4, 3.5.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121482 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121482 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/openssl/openssl/pull/33546
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-121482
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-121482"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenSSL OpenSSL
From 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-121482 |
| Record | NVD · CVE-2026-121482 |
| Other links 1 | |
| Patch | GitHub · openssl/openssl · Pull request #33546 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121482
Is CVE-2026-121482 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
Which versions are affected by CVE-2026-121482?
OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10.Source: cve.now feed data
How do I fix CVE-2026-121482?
Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.Source: cve.now feed data