Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in UTT HiPER 1200GW firmware can let a low-privileged authenticated attacker corrupt memory by submitting an oversized configuration value. Successful exploitation could compromise confidentiality, integrity, and availability. Public exploit material increases urgency, although the supplied sources do not establish active exploitation.
Executive priority
Treat as an urgent asset-discovery and containment issue because impact is critical and exploit material is public. Prioritize externally reachable devices first. Establish ownership, restrict access immediately, and obtain authoritative UTT remediation guidance. Do not interpret the public exploit reference as proof that your environment was attacked.
Technical view
CVE-2026-76003 is a stack-based buffer overflow in the strcpy handling of the timestart argument at /goform/formGroupConfig. UTT HiPER 1200GW versions through 2.5.3-170306 are reported affected. The CVSS 3.1 score is 9.9, with network access, low complexity, low privileges, no user interaction, and scope change.
Likely exposure
Exposure exists where an affected device permits network access to the vulnerable form handler and an attacker has low-privileged credentials. Internet-accessible administration paths present the greatest concern, but internal access, stolen credentials, or compromised accounts may also create risk. The supplied sources provide no deployment prevalence data.
Exploitation context
Public exploit material is referenced, demonstrating disclosure beyond a theoretical weakness. However, the CVE is not listed as CISA KEV in the supplied bundle, and no cited source confirms active exploitation in the wild. Authentication is required according to the CVSS vector.
Researcher notes
The record attributes unsafe strcpy processing of timestart to a stack overflow and maps it to CWE-119 and CWE-121. Evidence supports remote, authenticated triggering and severe potential impact. The supplied material does not name a fixed version, vendor patch, affected configuration prerequisites, reliable indicators of compromise, or confirmed exploitation telemetry.
Mitigation direction
- Identify UTT HiPER 1200GW devices running firmware through 2.5.3-170306.
- Check UTT guidance for corrected firmware or vendor-approved remediation; none is identified in the supplied sources.
- Restrict device interfaces to trusted administrative networks and approved management hosts.
- Remove unnecessary external exposure and enforce strong, unique credentials.
- Monitor for unusual requests to /goform/formGroupConfig and unexpected device instability.
Validation and detection
- Confirm each device model and installed firmware version using trusted inventory or administrative records.
- Verify whether /goform/formGroupConfig is reachable from internet, user, and untrusted network segments.
- Review access logs for unusual formGroupConfig requests or abnormal timestart values.
- Check authentication records for unknown accounts, suspicious logins, or credential misuse.
- After remediation, confirm the vulnerable firmware is absent and network restrictions remain effective.
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-76003 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-391919 | UTT HiPER 1200GW formGroupConfig strcpy stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-391919 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-76003 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #877884 | UTT HiPER 1200GW <=v2.5.3-170306 Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://github.com/7wkajk/CVE-VUL/blob/main/105.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.