# CVE-2026-96274: Uncaught exception in Baicells Nova 430H

> An unauthenticated attacker within radio range can cause a temporary service disruption by sending a malformed uplink message that crashes the signaling association.

- **Severity:** High 8.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-r2c9-ccv7-wg9h

## What is CVE-2026-96274?

CVE-2026-96274 is a high-severity denial of service vulnerability in Baicells Nova 430H eNodeB  (model pBS3101SH), published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Baicells Nova 430H, an unauthenticated device within radio range can send a malformed uplink message during connection setup that contains an invalid NAS payload. Because the eNodeB does not properly validate this payload, it forwards the message to the core network, which can trigger a shutdown of the signaling association for the cell. This results in a temporary service disruption until the eNodeB and core network re-establish connectivity.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-96274 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96274 is a high-severity denial of service vulnerability in Baicells Nova 430H eNodeB  (model pBS3101SH), published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96274 in the wild and no public exploit code.

Affected product: Baicells Nova 430H eNodeB  (model pBS3101SH). 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-96274/ (Markdown: https://insights.sbomify.com/CVE-2026-96274/index.md)
```

## Sources

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

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