# CVE-2026-42767: NULL Pointer Dereference in CRMF EncryptedValue Decryption

> A malicious CMP server can crash OpenSSL CMP clients via a crafted response, causing denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** ALPINE-CVE-2026-42767, AZL-89787, AZL-89870, AZL-89922, BELL-CVE-2026-42767, CLSA-2026-1782983109, DEBIAN-CVE-2026-42767, ECHO-86de-f803-ef79, GHSA-gxhg-7jx8-m22j, JLSEC-2026-1139, MINI-74p3-fj72-g9x2, MINI-c2qm-45cv-hv74, SUSE-SU-2026:22437-1, SUSE-SU-2026:22449-1, SUSE-SU-2026:3004-1, UBUNTU-CVE-2026-42767

## What is CVE-2026-42767?

CVE-2026-42767 is a medium-severity vulnerability in Openssl Openssl, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Issue summary: An attacker-controlled CMP (Certificate Management Protocol)
server could trigger a NULL pointer dereference in a CMP client application.

Impact summary: A NULL pointer dereference causes a crash of the
application and a Denial of Service.

An attacker controlling a CMP server (or acting as a man-in-the-middle) could
craft a CMP response containing a CRMF (Certificate Request Message Format)
CertRepMessage with an EncryptedValue structure where the symmAlg field
has an algorithm OID but no parameters field. When the OpenSSL CMP client
processes this response, the NULL dereference occurs, causing a crash of
the CMP client.

Applications that process untrusted CMP/CRMF messages may be affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this
issue, as the affected code is outside the OpenSSL FIPS module boundary.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-42767?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl-3` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 3.1.4-150600.5.56.1 |
| `openssl-3` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 3.1.4-150600.5.56.1 |
| `openssl-3` | SUSE:Linux Micro 6.0 | All versions | 3.1.4-15.1 |
| `openssl-3` | SUSE:Linux Micro 6.1 | All versions | 3.1.4-slfo.1.1_11.1 |

Products: Openssl Openssl.

## How do I fix CVE-2026-42767?

Apply the vendor's patch.

## Is CVE-2026-42767 being exploited?

There is no known exploitation of CVE-2026-42767 in the wild and no public exploit code.

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42767 and fix it if it is affected.

What it is: CVE-2026-42767 is a medium-severity vulnerability in Openssl Openssl, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42767 in the wild and no public exploit code.

Affected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42767/ (Markdown: https://insights.sbomify.com/CVE-2026-42767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42767
- OSV: https://osv.dev/vulnerability/CVE-2026-42767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42767/
Summaries are generated and may contain mistakes; the official description above is the record.