CVE-2026-45445: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-v446-xwfm-x7mr
Share
CVSS 7.5
CWE-325
Published
Advisory Summary

CVE-2026-45445 is a HIGH (CVSS 7.5) security vulnerability vulnerability (CWE-325: Missing Cryptographic Step) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-45445 at a Glance

CVE Identifier CVE-2026-45445
GHSA Identifier GHSA-v446-xwfm-x7mr
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-325: Missing Cryptographic Step
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-45445

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-45445, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-325: Missing Cryptographic Step, where the product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-45445 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-45445
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/983d54b5cce8d16147548ed1a37892d1720bbab6
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/983d54b5cce8d16147548ed1a37892d1720bbab6
openssl-library.org/news/secadv/2026060... WEB
https://openssl-library.org/news/secadv/20260609.txt

Frequently Asked Questions

What is CVE-2026-45445?
CVE-2026-45445 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-325: Missing Cryptographic Step.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-45445?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-45445?
CVE-2026-45445 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-45445?
CVE-2026-45445 is classified under CWE-325: Missing Cryptographic Step (The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.).
How can I check Maven dependencies for CVE-2026-45445?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v446-xwfm-x7mr",
  "modified" : "2026-06-10T09:31:57Z",
  "published" : "2026-06-09T18:30:48Z",
  "aliases" : [ "CVE-2026-45445" ],
  "details" : "Issue summary: When an application drives an AES-OCB context through the\npublic EVP_Cipher() one-shot interface, the application-supplied\ninitialisation vector (IV) is silently discarded.\n\nImpact summary: Every message encrypted under the same key uses the\nsame effective nonce regardless of the IV supplied by the caller,\nresulting in (key, nonce) reuse and loss of confidentiality.  If the\nsame code path is used to compute the authentication tag, the tag\ndepends only on the (key, IV) pair and not on the plaintext or\nciphertext, allowing universal forgery of arbitrary ciphertext from a\nsingle captured message.\n\nOpenSSL provides two ways to drive a cipher: the documented streaming\ninterface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level\none-shot, EVP_Cipher(), whose documentation explicitly recommends\nagainst use by applications in favour of EVP_CipherUpdate() and\nEVP_CipherFinal_ex().  The OCB provider's streaming handler flushes\nthe application-supplied IV into the OCB context before processing\ndata; the one-shot handler did not.  Every call to EVP_Cipher() on an\nAES-OCB context therefore ran with the all-zero key-derived offset\nstate left by cipher initialisation, regardless of the caller's IV.\n\nIf EVP_EncryptFinal_ex() is subsequently used to obtain the\nauthentication tag, the deferred IV setup runs at that point and\nclears the running checksum that should have been accumulated over the\nplaintext.  The resulting tag is a function of (key, IV) only and\nverifies against any ciphertext produced under the same (key, IV)\npair.\n\nThe OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a\nTLS cipher suite, and libssl does not call EVP_Cipher() in any case.\nApplications that drive AES-OCB through the documented streaming AEAD\nAPI (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected.  Only\napplications that combine the AES-OCB cipher with the EVP_Cipher()\none-shot API are vulnerable.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by\nthis issue, as AES-OCB is outside the OpenSSL FIPS module boundary.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45445"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/983d54b5cce8d16147548ed1a37892d1720bbab6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/983d54b5cce8d16147548ed1a37892d1720bbab6"
  }, {
    "type" : "WEB",
    "url" : "https://openssl-library.org/news/secadv/20260609.txt"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-325" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-09T17:17:18Z"
  }
}