Motor.NET: Denial of Service via unhandled JSON deserialization exception
Summary
Motor.NET before 0.19.0 does not catch JsonSerializationException during message deserialization. A remote attacker who can publish messages to a queue or topic consumed by the service can send structurally valid JSON that does not match the handler's expected type. This stops the service, and because the unacknowledged message is redelivered on restart, the service enters a permanent crash loop. The impact is limited to availability.
Affected
- Motor.NET versions before 0.19.0
- Attacker needs publish rights on the message broker consumed by the service; no privileges on the application are required
Fixed in
- Motor.NET 0.19.0 (fix in commit d5aee7db8e0de3cec95bf8744c499c2ff6019c0c, PR #1785)
Workaround
- Unknown. No vendor workaround was found in the sources.
- Interim measures (not from vendor sources): restrict which identities can publish to consumed queues and topics; validate message structure before it reaches the handler; configure restart backoff or dead-lettering so a single bad message cannot cause a restart loop.
Exploitation
- Known exploitation in the wild: none found in the sources reviewed.
- Public proof of concept: none found.
- CISA SSVC: exploitation none, automatable yes, technical impact partial.
Our recommendation
- Identify all Motor.NET deployments and check package versions in lockfiles and deployed manifests.
- Upgrade Motor.NET to 0.19.0 or later.
- Until patched, limit publish rights on consumed queues and topics to trusted producers.
- Monitor services for repeated restarts as an indicator of exploitation.
- Prioritise internal services where broker publish access is broad or the broker is reachable from outside the organisation.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- GitHub release v0.19.0 github.com
- Fix commit d5aee7d github.com
- Pull request #1785 github.com
- VulnCheck advisory www.vulncheck.com
- OSV CVE-2026-112332 vulners.com
- CVE-2026-112332 threatint cve.threatint.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 1 Nov 2026, 00:37.
Original description (NVD)
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.
NVD references (4)
- https://github.com/GDATASoftwareAG/motornet/commit/d5aee7db8e0de3cec95bf8744c499c2ff6019c0c
- https://github.com/GDATASoftwareAG/motornet/pull/1785
- https://github.com/GDATASoftwareAG/motornet/releases/tag/v0.19.0
- https://www.vulncheck.com/advisories/motor-net-denial-of-service-via-jsonnet-deserialization
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.