Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9381 is a critical buffer overflow in the Edimax BR-6675nD router firmware 1.12. A remote authenticated attacker may be able to crash or compromise the device through its PPPoE setup handler. Public exploit material exists, and the source bundle reports no vendor response.
Executive priority
Treat this as urgent for any deployed BR-6675nD 1.12 device. Public exploit availability and lack of vendor response raise operational risk, especially for exposed router administration surfaces.
Technical view
The issue affects /goform/formPPPoESetup in the POST request handler. Manipulating the pppUserName argument can trigger a buffer overflow, mapped to CWE-119 and CWE-120. The CVSS 2.0 vector is 9.0 with network access, low complexity, authenticated access, and complete confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Edimax BR-6675nD devices running firmware 1.12 where the management interface and PPPoE setup function are reachable to authenticated users. Risk increases sharply if administration is exposed to untrusted networks or weak credentials are used.
Exploitation context
The source bundle states the exploit is public and may be used, but KEV is false and no cited source confirms active exploitation. Authentication is required according to the CVSS vector and VulDB CTI tags.
Researcher notes
Evidence supports a buffer overflow in the PPPoE setup POST handler via pppUserName, with authenticated remote access required. The sources do not provide a confirmed patch, active exploitation evidence, or vendor remediation statement.
Mitigation direction
- Inventory Edimax BR-6675nD devices and confirm firmware version 1.12 exposure.
- Check Edimax guidance regularly; no vendor fix is named in the provided sources.
- Restrict router management access to trusted networks or VPN-only administration.
- Disable internet-facing administration where possible.
- Harden administrator credentials and remove unused accounts.
- Consider isolation or replacement if no supported firmware becomes available.
Validation and detection
- Confirm whether any BR-6675nD devices run firmware 1.12.
- Verify the management interface is not reachable from untrusted networks.
- Review access controls for authenticated administration paths.
- Check device logs for unexpected PPPoE configuration changes or crashes.
- Monitor vulnerability feeds for vendor updates or KEV status 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-9381 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-365344 | Edimax BR-6675nD POST Request formPPPoESetup buffer overflow CVE reference, VulDB · vdb-entry, technical-description
- VDB-365344 | CTI Indicators (IOB, IOC, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #811559 | EDIMAX BR-6675nD BR-6675nD v1.12 Buffer Overflow CVE reference, VulDB · third-party-advisory
- https://lavender-bicycle-a5a.notion.site/EDIMAX-BR-6675nD-formPPPoESetup-34b53a41781f803faf50d4caf940d2dc?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.