Skip to content

CWE-393 · Input Validation and Logic

Return of Wrong Status Code

8CVEs

8 CVEs with CWE-393 as their weakness

CVEs with CWE-393, Most likely exploited
CVE · most likely exploitedCVSSEPSSPublished
CVE-2023-37897Server-side Template Injection (SSTI) in gravgetgrav · grav · CVSS 7.2 · 2023-07-187.22.8%2023-07-18
CVE-2025-5987Libssh: invalid return code for chacha20 poly1305 with openssl backendRedhat · libssh · CVSS 8.1 · 2025-07-078.11.7%2025-07-07
CVE-2020-5401Cloud Foundry GoRouter is vulnerable to cache poisoningCloud Foundry · Routing · CVSS 5.3 · 2020-02-275.31.0%2020-02-27
CVE-2024-49117Windows Hyper-V Remote Code Execution VulnerabilityMicrosoft · Windows 11 version 22H2 · CVSS 8.8 · 2024-12-108.81.0%2024-12-10
CVE-2025-32414In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in x…xmlsoft · libxml2 · CVSS 5.6 · 2025-04-085.60.4%2025-04-08
CVE-2026-92821Sssd: sssd: access control bypass via premature ldap access rule evaluationRed Hat · Red Hat Enterprise Linux 10 · CVSS 6.8 · 2026-10-066.80.3%2026-10-06
CVE-2025-24531In OpenSC pam_pkcs11 before 0.6.13, pam_sm_authenticate() wrongly returns PAM_IGNORE in many error situations (such as an error triggered by a smartcard before login), allowing au…OpenSC project · pam_pkcs11 · CVSS 6.7 · 2026-01-166.70.2%2026-01-16
CVE-2026-53092bpf: Fix linked reg delta tracking when src_reg == dst_regLinux · Linux · CVSS 7.8 · 2026-06-247.80.1%2026-06-24

EPSS is the probability of exploitation in the next 30 days (FIRST). Data as of 2026-11-14.

Updated AboutDevelopersSign in