Skip to main content
VulnerabilityPublished

CVE-2026-18897: UTT HiPER 1250GW · Stack-based Buffer Overflow

Affects UTT HiPER 1250GWSource CVE Database V5

0
Compare

Public exploit available · CVSS 8.7 High.

Data as of 3 Nov 2026, 10:57 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
UTTHiPER 1250GWAffected
  • =3.2.7-210907-180535
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:utt:hiper_1250gw:*:*:*:*:*:*:*:*

AI-suggested

In the absence of an official fix, users should consider mitigating exposure by restricting network access to the affected device, disabling vulnerable services if possible, and monitoring for suspicious activity related to this vulnerability.

Description

CVE-2026-18897 is a high-severity stack-based buffer overflow vulnerability in the UTT HiPER 1250GW device, specifically in the strcpy function within /goform/getOneApConfTempEntry. The vulnerability is triggered by manipulating the tempName argument and can be exploited remotely without user interaction. The affected version is exactly 3.2.7-210907-180535. Although an exploit is publicly available, there is no vendor response or official patch at this time.

References

Community reviews

Loading reviews…