Analyst readout for executives and security teams
Plain-English summary
This is a critical flaw in UTT HiPER 1250GW web management. A remote authenticated attacker could trigger memory corruption through the Profile field and potentially gain full control. Public exploit material exists, but the supplied sources do not show active exploitation or a vendor patch.
Executive priority
Treat this as urgent if the device exists in the environment, especially if management is remotely reachable. Prioritize exposure reduction while awaiting or confirming vendor remediation.
Technical view
CVE-2026-9631 is a stack-based buffer overflow in /goform/formConfigFastDirectionW, tied to strcpy handling of the Profile argument. Sources list UTT HiPER 1250GW up to firmware 3.2.7-210907-180535 as affected. CVSS v2 is 9.0 with network access, low complexity, and single authentication required.
Likely exposure
Exposure is most likely where UTT HiPER 1250GW web management is enabled and reachable from untrusted networks. Risk is higher for internet-facing, partner-facing, or weakly controlled administrative interfaces.
Exploitation context
The source bundle says an exploit is public and may be used. CVE KEV status is false, and no provided source confirms active exploitation in the wild.
Researcher notes
The evidence supports a strcpy-based stack overflow in the Profile parameter, mapped to CWE-119 and CWE-121. The CVSS vector indicates authenticated remote attack conditions. Patch status is not established in the supplied sources.
Mitigation direction
- Check UTT or device supplier guidance for patched firmware or official workarounds.
- Restrict web management access to trusted administrative networks only.
- Remove internet exposure for the management interface immediately.
- Review and tighten administrative account access to affected devices.
- Monitor device logs for unusual web management activity.
Validation and detection
- Inventory UTT HiPER 1250GW devices and record firmware versions.
- Confirm whether firmware is 3.2.7-210907-180535 or earlier.
- Verify web management is not reachable from the public internet.
- Check whether administrative access requires strong, unique credentials.
- Review perimeter scans and firewall rules for exposed management ports.
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-121: 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-9631 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-365740 | UTT HiPER 1250GW Web Management formConfigFastDirectionW strcpy stack-based overflow CVE reference, VulDB · vdb-entry, technical-description
- VDB-365740 | CTI Indicators (IOB, IOC, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #818375 | UTT HiPER 1250GW <=v3.2.7-210907-180535 Buffer Overflow CVE reference, VulDB · third-party-advisory
- https://github.com/zhouguobing-maker/cve/blob/main/11.md 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.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.