Live › vulnerability › CVE-2026-112332
Go to dashboardMotor.NET versions before 0.19.0 do not catch JsonSerializationException in the JSON deserializer, so a malformed-for-type message stops the consuming service. The unacknowledged message is redelivered on restart, so the service crashes in a loop.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check whether the project references the Motor.NET package and its version (for example in the .csproj or packages.lock.json) and confirm it is below 0.19.0.
Upgrade Motor.NET to 0.19.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-112332")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.