Quick answers
- Is CVE-2026-18330 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18330 being exploited in the wild.
- How severe is CVE-2026-18330?
- Informational severity, with a CVSS score of 6.1, published 3 September 2026.
- Which products and versions are affected?
- TP-Link Archer AX55 v4 prior to 1.2.1 Build 20260527.
- Is there a fix for CVE-2026-18330?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-18330 attacked?
- It is attacked from the adjacent network.
- Am I affected by CVE-2026-18330?
- Check whether you run TP-Link Archer AX55 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A hard-coded cryptographic key vulnerability exists in the web authentication module of TP-Link Archer AX55 v4. The vulnerability stems from the use of a shared RSA-1024 private key embedded in the firmware that is used for password encryption during HTTP login sessions. An attacker on the local network can passively capture HTTP login traffic, extract the RSA-encrypted password, and decrypt it using the known private key. The impact is further amplified by weak AES session key generation, reducing the computational effort required to compromise session confidentiality. Attack requires network adjacency (LAN access) and packet capture capability, but no authentication or user interaction. Successful exploitation discloses the administrator password and enables full compromise of device administration. The fix is available in firmware version 1.2.1 Build 20260527 or later.
Affected products
- TP-Link Archer AX55 v4 prior to 1.2.1 Build 20260527
Timeline
- 2026-09-03: disclosed