Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9443 is a critical buffer overflow in Edimax BR-6478AC firmware 1.23. A remote authenticated attacker could potentially compromise confidentiality, integrity, and availability. Public exploit material is referenced, but the source bundle does not show confirmed active exploitation or a vendor fix.
Executive priority
Treat as urgent for any affected internet-facing or broadly reachable router. Prioritize discovery and exposure reduction now, because public exploit material exists and no vendor response or fix is cited.
Technical view
The issue affects /goform/formL2TPSetup in the POST request handler. Manipulating the L2TPUserName argument can trigger a buffer overflow. CVSS v2 is 9.0 with network access, low complexity, authentication required, proof-of-concept exploit maturity, and unconfirmed report confidence.
Likely exposure
Exposure is likely limited to Edimax BR-6478AC devices running firmware 1.23, especially where administrative or L2TP configuration endpoints are reachable from untrusted networks. References also mention BR6478ACV2, so confirm model and firmware precisely.
Exploitation context
The bundle says the exploit has been publicly disclosed and may be used. It does not show CISA KEV listing, confirmed exploitation in the wild, or vendor acknowledgement. Authentication appears required from the CVSS vector.
Researcher notes
Key uncertainty is vendor status. The CVSS vector indicates authenticated remote exploitation, while the description emphasizes remote initiation. Do not assume unauthenticated exploitation or active campaigns without additional evidence.
Mitigation direction
- Identify Edimax BR-6478AC devices running firmware 1.23.
- Check Edimax guidance for fixed firmware or official mitigations.
- Restrict management and configuration access to trusted networks only.
- Disable unnecessary remote administration or L2TP configuration exposure.
- Replace or isolate affected devices if no vendor fix is available.
Validation and detection
- Inventory router model, hardware revision, and firmware version.
- Confirm whether /goform/formL2TPSetup is reachable from untrusted networks.
- Review administrative access logs for unusual configuration attempts.
- Verify access controls require trusted administrative authentication.
- Track vendor and CVE updates for remediation changes.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-9443 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR 8 10 VulDB CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R 2.8 5.9 VulDB CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R 2.8 5.9 VulDB CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P — — VulDB Vulnerability scoring details
Base CVSS 4.0 score
8.7 HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
8.8 HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 3.0 score
8.8 HighVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 2.0 score
9 CriticalVector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- VDB-365424 | Edimax BR-6478AC POST Request formL2TPSetup buffer overflow CVE reference, VulDB · vdb-entry, technical-description
- VDB-365424 | CTI Indicators (IOB, IOC, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #818452 | Edimax BR6478ACV2 BR6478ACV2_v1.23 Buffer Overflow CVE reference, VulDB · third-party-advisory
- https://lavender-bicycle-a5a.notion.site/EDIMAX-BR6478ACV2-formL2TPSetup-34b53a41781f809e9c30c1260cc5d92e?source=copy_link CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.