CVE-2025-15608 — CVE & Security Advisory Radar

🎯 CVE-2025-15608 HIGH 7.7 🔥 EPSS 64% 🇪🇺 EUVD

📄 .md Alle CVEs anzeigen ✕

CVE-2025-15608 | This vulnerability in AX53 v1, AX55 v4 and AX55 v4.6 results from insufficient input sanitization in the device’s probe handling logic, where unvalidated parameters can trigger a stack-based buffer overflow that causes the affected service to crash and, under specific conditions, may enable remote code execution through complex heap-spray techniques. Successful exploitation may result in repeated service unavailability and, in certain scenarios, allow an a

This vulnerability in AX53 v1, AX55 v4 and AX55 v4.6 results from insufficient input sanitization in the device’s probe handling logic, where unvalidated parameters can trigger a stack-based buffer overflow that causes the affected service to crash and, under specific conditions, may enable remote code execution through complex heap-spray techniques.

Successful exploitation may result in repeated service unavailability and, in certain scenarios, allow an attacker to gain control of the device.

Klassifikation & Betroffenheit:

TP-Link Systems Inc. AX55 v4.6 0 <(US)_1.2.1 Build 20260527AX53 v1 0 <251029AX55 v4 0 <(US)_1.2.1 Build 20260527tp-link archer_ax53_firmware 1.0

Improper Restriction of Operations within the Bounds of a Memory Buffer 🎯 High

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

🛡️ Empfohlene Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow prot…

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-10 · Buffer Overflow via Environment Variable… (High) CAPEC-14 · Client-side Injection-induced Buffer Ove… (High) CAPEC-24 · Filter Failure through Buffer Overflow (High) CAPEC-42 · MIME Conversion (High) CAPEC-44 · Overflow Binary Resource File (Very High) CAPEC-45 · Buffer Overflow via Symbolic Links (High) CAPEC-100 · Overflow Buffers (Very High) CAPEC-123 · Buffer Manipulation (Very High)

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2026-15315 8.7 CVE-2025-30237 8.7 CVE-2026-12935 8.7 CVE-2026-8697 8.7 CVE-2026-34121 8.7

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2025

Veröffentlicht 03/2026

Heute 06.09.

CVSS-Vektor-Analyse: 7.7

AV · Angriffsvektor Benachbart

AC · Komplexität Hoch

PR · Privilegien Keine

UI · Interaktion Keine

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

Veröffentlicht:20.03.2026

Aktualisiert:12.08.2026 20:17

Assigner (CNA):TPLink

EUVD-ID:EUVD-2025-208907

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	2026-08-29	2026-09-05
≥90 %	4	0
≥50 %	4	0
≥10 %	3	0
<10 %	304	300

7.7 HIGH

🇪🇺 EUVD

EPSS

64%

CVE-2025-15608 🌐 Adjacent Network 🔓 Keine Authentifizierung nötig

TP-Link Systems Inc.

CVE-2025-15608 | This vulnerability in AX53 v1, AX55 v4 and AX55 v4.6 results from insufficient input sanitization in the device’s probe handling logic, where unvalidated parameters can trigger a stack-based buffer overflow that causes the affected service to crash and, under specific conditions, may enable remote code execution through complex heap-spray techniques. Successful exploitation may result in repeated service unavailability and, in certain scenarios, allow an a

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

20.03.2026

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub