openssl-src heap memory corruption with RSA private key operation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-2274: 48.23% estimated exploitation activity in the next 30 days; percentile 98.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X8664 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys running on machines supporting AVX512IFMA instructions of the X8664 architecture are affected by this issue.

Published by the source

2 Jul 2022, 00:00 UTC

Last modified by the source

13 Jun 2023, 19:52 UTC

Source last checked

26 Oct 2026, 15:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-735f-pg76-fxc4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-2274

Advisory: openssl-src heap memory corruption with RSA private key operation
IDs: CVE-2022-2274, GHSA-735f-pg76-fxc4
Record: https://patchnext.com/advisories/cve-2022-2274 (revision 1, source checked 26 Oct 2026, 15:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openssl-src 300.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io openssl-src: affected >= 300.0.8, < 300.0.9; fixed in 300.0.9

## Suggested inspection (read-only)
- crates.io openssl-src: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openssl-src.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-735f-pg76-fxc4 (GitHub-reviewed advisory GHSA-735f-pg76-fxc4 lists affected ranges: crates.io openssl-src >=300.0.8 <300.0.9)

Commands are suggestions: review each one before running it.