Security readout for executives and security teams
Plain-English summary
UTT HiPER 1250GW devices running firmware through build 3.2.7-210907-180535 contain a remotely reachable memory-corruption flaw in an HTTP handler. A low-privileged authenticated attacker could potentially compromise confidentiality, integrity, and availability. Public exploit material exists, increasing urgency, but the supplied sources do not establish active exploitation.
Executive priority
Prioritize immediate exposure reduction and vendor engagement. Internet-accessible or broadly reachable devices warrant emergency handling because impact is potentially complete and exploit information is public. Internally isolated devices still require prompt review. Do not claim compromise without evidence, but do not wait for confirmed active exploitation before restricting access.
Technical view
The /goform/aspApBasicConfigUrcp handler copies attacker-controlled pvid data with strcpy into a stack buffer, causing a stack-based overflow (CWE-119/CWE-121). CVSS 3.1 rates it 9.9: network-accessible, low complexity, low privileges, no user interaction, and potentially high impact across a changed security scope.
Likely exposure
Exposure is most likely where an affected UTT HiPER 1250GW management HTTP interface is reachable by untrusted networks or accounts. Exploitation requires low privileges according to the CVSS vector. The sources identify firmware through 3.2.7-210907-180535; they do not clarify default exposure, affected configurations, or whether later firmware is fixed.
Exploitation context
A technical write-up or exploit has been publicly disclosed, making independent reproduction more plausible. However, the CVE is not listed as CISA KEV in the supplied bundle, and no cited evidence confirms exploitation in the wild. Treat public exploit availability as elevated risk, not proof of active attacks.
Researcher notes
The core evidence identifies unsafe strcpy use on the pvid argument in an HTTP handler and remote initiation with low privileges. Public disclosure is reported, but reliable exploitation, code-execution outcome, affected configuration details, and a vendor-fixed release are not established. Validation should remain non-destructive and focus on inventory, reachability, firmware, logs, and vendor guidance.
Mitigation direction
- Inventory UTT HiPER 1250GW devices and record their exact firmware builds.
- Restrict management HTTP access to trusted administrative networks and authorized accounts.
- Prevent internet exposure using network controls while awaiting confirmed vendor remediation.
- Check UTT guidance for fixed firmware or an approved workaround; none is identified in the supplied sources.
- Monitor affected devices for unexpected configuration changes, crashes, or administrative activity.
Validation and detection
- Confirm each identified device model and firmware version against the affected range.
- Verify the management HTTP interface is not reachable from untrusted networks.
- Review account permissions and remove unnecessary low-privileged management access.
- Inspect logs and monitoring data for unusual requests, crashes, restarts, or configuration changes.
- Confirm any vendor-provided update or workaround is documented and successfully applied.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-76004 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.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R3.16VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R3.16VulDBCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P——VulDBAV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR810VulDBVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 3.0 score
9.9CriticalVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R
Base CVSS 2.0 score
9CriticalVector: 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 timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-391920 | UTT HiPER 1250GW HTTP aspApBasicConfigUrcp strcpy stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-391920 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-76004 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #877885 | UTT HiPER 1250GW <=v3.2.7-210907-180535 Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://github.com/7wkajk/CVE-VUL/blob/main/106.mdCVE 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.