Categories
CVE-2026-45784 high CVSS 7.1

Vulnerability in openssl (CVE-2026-45784)

Summary

Vulnerability in openssl (CVE-2026-45784). Data can be tampered with by attackers. Mitigation: upgrade to 0.10.80 or later.

Original description

The description as published by the source.

CipherCtxRef::cipher_update_inplace incorrectly sized output buffers when used with AES key-wrap-with-padding ciphers (EVP_aes_{128,192,256}_wrap_pad). For a non-multiple-of-8 input, OpenSSL writes up to 7 bytes past the end of the caller's buffer or Vec, producing attacker-controllable heap corruption when the plaintext length is attacker-influenced.

This only impacts users using AES key-wrap-with-padding ciphers.

This method was missed in the fix for GHSA-xv59-967r-8726

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45784 has been found in openssl.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade openssl to 0.10.80 or later.
If unsure, ask your IT team or search "openssl CVE-2026-45784" on the vendor's site.

CVE-2026-45784 (openssl) — CWE-131 / CVSS v3 7.1
Attack vector: local / no user interaction
Patched: 0.10.80 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-131) exists in openssl.

📍 Affected scope

Check the vendor advisory for the affected versions of openssl.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 0.10.80.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openssl' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'openssl' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openssl を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade openssl to 0.10.80

    ステージング環境で 0.10.80 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust openssl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.10.80"}]}]
crates.io openssl
[{"type":"SEMVER","events":[{"introduced":"0.10.50"},{"fixed":"0.10.80"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details