CWE-167 Improper Handling of Additional Special Element

base

The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.

01

parent weaknesses

Broader classes this is a kind of.

02

vulnerabilities (7)

Known CVEs related to this entry.

IDseverity exploitable
CVE-2023-4809UShigh7.5—
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,…
CVE-2023-0643USmedium6.1—
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
CVE-2023-3580USmedium4.3—
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
CVE-2026-53092US——
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix linked reg delta tracking when src_reg == dst_reg Consider the case of rX += rX where src_reg and dst…
CVE-2026-53090US——
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into s…
CVE-2025-25006US——
Improper handling of additional special element in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
CVE-2025-30656US——
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 S…
03

source

Where this definition is published.

scry

Weaknesses like this turn up in real, exploitable exposures. See what is exposed on your perimeter with a free passive scan.

Free scan