# CVE-2026-31256: Null dereference in n/a

> An attacker can crash and reboot the MERCURY IP camera by sending a malformed RTSP SETUP request, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 27 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-jhq8-6g6m-wm24

## What is CVE-2026-31256?

CVE-2026-31256 is a high-severity vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A null pointer dereference vulnerability exists in the RTSP service of the MERCURY MIPC252W 1.0.5 Build 230306 Rel.79931n. During the processing of a SETUP request for the path rtsp://<IP>:554/stream1/track2, the device fails to properly validate the Transport header field. When this header is improperly constructed, the RTSP service can dereference a NULL pointer during request parsing. Successful exploitation causes the device to crash and automatically reboot.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Mercurycom Mipc252w Firmware.

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

No fix has been published for CVE-2026-31256 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31256 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31256 exists.

## Other vulnerabilities in n/a

- [CVE-2026-35903](https://insights.sbomify.com/CVE-2026-35903/): Auth bypass in n/a (critical 9.8)
- [CVE-2026-35902](https://insights.sbomify.com/CVE-2026-35902/): Denial of service in n/a (medium 6.2)
- [CVE-2026-35901](https://insights.sbomify.com/CVE-2026-35901/): Denial of service in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31256 is a high-severity vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31256 exists.

Affected product: n/a. 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-31256/ (Markdown: https://insights.sbomify.com/CVE-2026-31256/index.md)
```

## Sources

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

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