CWE-167— Improper Handling of Additional Special Element
The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.— MITRE CWE catalog
5 active CVEs classified under this weakness category. Sourced from NVD, GHSA, and vendor advisories. Full definition on MITRE →
CVEs classified under CWE-167page 1 of 1
- CVE-2023-0643MEDIUMCVSS 6.1EG 6.12023-02-02
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
- CVE-2023-3580MEDIUMCVSS 4.3EG 5.42023-07-10
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
- CVE-2023-4809HIGHCVSS 7.5EG 7.52023-09-06
In pf packet processing with a 'scrub fragment reassemble' rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed. That is, a packet with multiple fragment extension headers would not…
- CVE-2025-25006MEDIUMCVSS 5.3EG 5.32025-08-12
Improper handling of additional special element in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
- CVE-2025-30656HIGHCVSS 7.5EG 7.52025-04-09
An Improper Handling of Additional Special Element vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series with MS-MPC, MS-MIC and SPC3, and SRX Series, allows an unauthenticated, network-based attacke…
Map vulnerabilities like CWE-167 to your infrastructure
EchelonGraph correlates every CVE — across CWE-167 and 150+ other weakness categories — against the assets you actually run. See blast radius, fix versions, and remediation steps in one graph.
Start Free Scan →