WhisperX tag archive

#DoS Vulnerability

This page collects WhisperX intelligence signals tagged #DoS Vulnerability. It is designed for humans, search engines, and AI agents: each item links to a canonical source-backed record with sector, source, timestamp, credibility, and exportable structured data.

Latest Signals (4)

The Lab · 2026-03-30 18:27:28 · GitHub Issues

1. AutoMapper v15 Security Update Patches Critical DoS Vulnerability (CVE-2026-32933)

A critical security vulnerability in the widely-used AutoMapper library has been patched, forcing a major version jump from 12.0.1 to 15.1.3. The flaw, tracked as CVE-2026-32933, exposes applications to Denial of Service (DoS) attacks. The core issue lies in the library's handling of object mapping: when processing dee...

The Lab · 2026-03-31 10:27:08 · GitHub Issues

2. AutoMapper v15 Security Update Patches Critical DoS Vulnerability (CVE-2026-32933)

A critical security vulnerability in the widely-used AutoMapper library exposes countless .NET applications to potential Denial of Service (DoS) attacks. The flaw, tracked as CVE-2026-32933, stems from the library's handling of deeply nested object graphs. During mapping operations, AutoMapper employs recursive method ...

The Lab · 2026-04-25 18:54:06 · GitHub Issues

3. node-forge Patches Critical DoS Vulnerability in BigInteger.modInverse() — CVE-2026-33891

The node-forge JavaScript cryptography library has released version 1.4.0, patching a high-severity Denial of Service vulnerability (CVE-2026-33891) in its BigInteger.modInverse() function. The flaw, discovered by researcher Kr0emer, stems from an infinite loop triggered when modInverse() receives a zero value as input...

The Lab · 2026-05-07 09:31:39 · GitHub Issues

4. jackson-core Async Parser Bypasses Number Length Constraint, Raising DoS Risk

A vulnerability in the non-blocking JSON parser of jackson-core allows input with arbitrarily long numbers to bypass the `maxNumberLength` constraint enforced by `StreamReadConstraints`. The standard synchronous parser correctly applies this limit, which defaults to 1000 characters, but the async parsing path fails to ...