CVE-2026-45445: AES-OCB IV Ignored on EVP_Cipher() Path
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.
- Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 20240524git3e722403cd16-18; azl3 openssl 3.3.7-1 on Azure Linux 3.0 3.3.7-3.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 20240524git3e722403cd16-18; azl3 openssl 3.3.7-1 on Azure Linux 3.0 3.3.7-3 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: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's streaming handler flushes the application-supplied IV into the OCB context before processing data; the one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero key-derived offset state left by cipher initialisation, regardless of the caller's IV. If EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at that point and clears the running checksum that should have been accumulated over the plaintext. The resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module boundary.
- ALSA-2026:25237
- ALSA-2026:25239
- openSUSE-SU-2026:11023-1
- openSUSE-SU-2026:21005-1
- RHSA-2026:25237
- RHSA-2026:25239
- RHSA-2026:42825
- RHSA-2026:55543
- RHSA-2026:59635
- RHSA-2026:59641
- RHSA-2026:62562
- RHSA-2026:62563
- RHSA-2026:62790
- RHSA-2026:67551
- RHSA-2026:71542
- RHSA-2026:83617
- RHSA-2026:84572
- RHSA-2026:84573
- RLSA-2026:25237
- RLSA-2026:25239
- Published
- Jun 9, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-325
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- 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.0.0 and later · before 3.0.21
- openssl openssl3.4.0 and later · before 3.4.6
- openssl openssl3.5.0 and later · before 3.5.7
- openssl openssl3.6.0 and later · before 3.6.3
- openssl openssl4.0.0
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
- 4.0.0 and later · before 4.0.1affected · semver
- 3.6.0 and later · before 3.6.3affected · semver
- 3.5.0 and later · before 3.5.7affected · semver
- 3.4.0 and later · before 3.4.6affected · semver
- 3.0.0 and later · before 3.0.21affected · 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.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-devel | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-libs | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-perl | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:9 | openssl | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-devel | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-libs | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-perl | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| Alpine:v3.21 | openssl | from 3.0.0 · before 3.3.7-r1 | 3.3.7-r1 |
| Alpine:v3.22 | openssl | from 3.0.0 · before 3.5.7-r0 | 3.5.7-r0 |
| Debian:12 | openssl | before 3.0.20-1~deb12u2 | 3.0.20-1~deb12u2 |
| Debian:13 | openssl | before 3.5.6-1~deb13u2 | 3.5.6-1~deb13u2 |
| Debian:14 | openssl | before 3.6.3-1 | 3.6.3-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.8.1 | 3.5.0-160000.8.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.5.3-6.1 | 3.5.3-6.1 |
| Red Hat:enterprise_linux_eus:10.0 | openssl | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-debuginfo | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-debugsource | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-devel | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-libs | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-perl | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux:10.2 | openssl | before 1:3.5.5-4.el10_2 | 1:3.5.5-4.el10_2 |
| Red Hat:enterprise_linux:10.2 | openssl-debuginfo | before 1:3.5.5-4.el10_2 | 1:3.5.5-4.el10_2 |
| Red Hat:enterprise_linux:10.2 | openssl-debugsource | before 1:3.5.5-4.el10_2 | 1:3.5.5-4.el10_2 |
+96
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-2026-42770Jun 9, 2026 · FFC-DH Peer Validation Uses Attacker-Supplied q14Monitor
- ← EarlierCVE-2026-42771Jun 9, 2026 · Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email()24Monitor
- Later →CVE-2026-45446Jun 9, 2026 · Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes19Monitor
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.0.21 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.4.6 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.7 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.3 | Vendor (CNA) |
| OpenSSL OpenSSL | 4.0.1 | Vendor (CNA) |
| azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 | 20240524git3e722403cd16-18 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 openssl 3.3.7-1 on Azure Linux 3.0 | 3.3.7-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:openssl | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| alpine:openssl | 3.3.7-r1 · Alpine:v3.21 | Package registry (OSV) |
| debian:openssl | 3.0.20-1~deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.3-6.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:chunkah | 0:0.6.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-devel | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-libs | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-perl | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl3 | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python-cryptography | 0:50.0.0-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-cryptography | 0:50.0.0-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| rocky linux:openssl | 1:3.5.5-4.el10_2 · Rocky Linux:10 | Package registry (OSV) |
| suse:openssl-3 | 3.1.4-14.1 · SUSE:Linux Micro 6.0 | 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.
No history yet (it accumulates with the daily EPSS job).
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.
- Viktor Dukhovniremediation developer
- Alex Gaynor (Anthropic)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-454460 days apartIncorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes19Monitor
- CVE-2025-69418133 days apartUnauthenticated/unencrypted trailing bytes with low-level OCB function calls16Monitor
- CVE-2026-427700 days apartFFC-DH Peer Validation Uses Attacker-Supplied q14Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0355 · Jun 10, 2026(OpenSSL Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-325 · Missing Cryptographic StepCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
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 (5 more)Show less
- github.com/openssl/openssl/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7
- github.com/openssl/openssl/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af
- github.com/openssl/openssl/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c
- github.com/openssl/openssl/commit/983d54b5cce8d16147548ed1a37892d1720bbab6
- openssl-library.org/news/secadv/20260609.txt
Vendor advisories and official records. Exploit/PoC links are deliberately left out.