LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22916: RE11S v1.11 was discovered to contain a stack overflow via the pppUserName parameter in the formPPPoESetup...

RE11S v1.11 was discovered to contain a stack overflow via the pppUserName parameter in the formPPPoESetup function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-22916 is a critical stack overflow in RE11S v1.11. A network-accessible, unauthenticated attack is rated possible by CVSS, with potential full confidentiality, integrity, and availability impact. Public sources do not state active exploitation or a vendor patch.

Executive priority

Prioritize identifying and isolating affected devices. The vulnerability is critical and remotely reachable by CVSS, but public sources do not confirm exploitation or a patch. Business urgency is highest for internet-exposed or unmanaged devices.

Technical view

The flaw is reported in the pppUserName parameter handled by the formPPPoESetup function. It is classified as CWE-120 and scored CVSS 3.1 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVE record lists limited product metadata, so asset identification may require manual firmware checks.

Likely exposure

Exposure is most likely where RE11S v1.11 devices are deployed and their management or PPPoE setup functionality is reachable over a network. The CVE data does not provide CPEs, broader version ranges, or deployment conditions.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source confirms active exploitation. A public GitHub reference exists, indicating technical details may be publicly available. Treat internet-exposed devices as urgent until vendor guidance is confirmed.

Researcher notes

Evidence is sparse: the CVE names RE11S v1.11 and the vulnerable parameter/function, but affected vendor/product metadata is marked n/a. Avoid assuming other models or versions are affected without vendor confirmation or validated firmware analysis.

Mitigation direction

  • Check Edimax or device vendor guidance for firmware updates or advisories.
  • Restrict device management access to trusted administrative networks only.
  • Disable remote administration if it is not required.
  • Remove internet exposure for RE11S management interfaces.
  • Consider replacement if no supported fixed firmware is available.

Validation and detection

  • Inventory environments for RE11S devices running firmware v1.11.
  • Confirm firmware versions through approved administrative methods.
  • Identify whether management interfaces are reachable from untrusted networks.
  • Review device logs for crashes, resets, or unexpected PPPoE changes.
  • Monitor CVE and vendor pages for updated remediation information.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-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 lookup
cve · low confidence lookup

CVE-2025-22916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-22916Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

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.