Cyber Resilience

CVE-2026-15429

Tp-Link Archer Vx1800V Firmware ≤ 0.16.0

Published
14 July 2026
Modified
06 August 2026
Patch / advisory
View advisory
CVSS Score v4 5.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0084 55th percentile
Risk Priority 30 floored blend · peak EPSS

Summary

CVE-2026-15429 is a medium-severity CRLF Injection (CWE-93) vulnerability in Tp-Link Archer Vx1800V Firmware. Its CVSS base score is 5.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A privilege escalation vulnerability exists in the HTTP authentication component in Archer VX1800v v1. Improper handling of user-controlled input may allow newline characters to be injected into internally constructed configuration data. An authenticated user with sufficient privileges may be able…

more

to modify account settings and gain elevated administrative privileges.

CWE(s)
CWE-93

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-15427Same product: Tp-Link Archer Vx1800V
CVE-2026-15428Same product: Tp-Link Archer Vx1800V
CVE-2023-49074Same vendor: Tp-Link
CVE-2024-48867Shared CWE-93
CVE-2024-21827Same vendor: Tp-Link
CVE-2026-3234Shared CWE-93
CVE-2026-30227Shared CWE-93
CVE-2026-6351Shared CWE-93
CVE-2026-5140Shared CWE-93
CVE-2025-0293Shared CWE-93

Affected Assets

tp-link
archer vx1800v firmware
2.0.0 · ≤ 0.16.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V4.2.4

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly stops untrusted data containing CRLF sequences from reaching the component that treats CRLF as a delimiter.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to block CRLF injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect CRLF flaws but does not itself implement the neutralization.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing special characters such as CRLF in inputs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe handling of untrusted data but do not prescribe specific CRLF controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require neutralization of CRLF sequences, fully addressing this weakness.

References