# CVE-2026-112332: Motor.NET < 0.19.0 Denial of Service via JsonNet Deserialization


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-pw68-j96j-jcjv

## What is CVE-2026-112332?

CVE-2026-112332 is a high-severity vulnerability in GDATASoftwareAG motornet, published on 22 Oct 2026. 

### Official description

Motor.NET before 0.19.0 contains an uncaught exception vulnerability in JsonNetDeserializer.Deserialize that allows a remote attacker who can publish to a consumed queue or topic to crash the service permanently by sending structurally valid JSON that does not match the handler's expected type. Attackers can exploit the fact that JsonSerializationException is not caught alongside JsonReaderException and InvalidCastException, causing TypedConsumerService.SingleMessageConsumeAsync to treat the error as CriticalFailure and call StopApplication, which combined with the unacknowledged message being redelivered on restart results in a permanent crash-loop.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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


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

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

## Is CVE-2026-112332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112332 is a high-severity vulnerability in GDATASoftwareAG motornet, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112332 in the wild and no public exploit code.

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

## Sources

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

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