Skip to main content
VulnerabilityPublished

CVE-2026-76988: liftoff-sr CIPster · Out-of-bounds Read

Affects liftoff-sr CIPsterSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
liftoff-srCIPsterAffected
  • =1802525be27d33e19a9a83c163e331a1d13b1892
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:liftoff-sr:cipster:*:*:*:*:*:*:*:*

AI-suggested

A patch identified by commit ea870a274bf68dfaa3f511f20e2fff6778fb7b74 has been released to fix this vulnerability. It is recommended to apply this patch promptly to remediate the issue. No additional mitigation guidance is provided or required.

Description

CVE-2026-76988 is an out-of-bounds read vulnerability in the liftoff-sr CIPster product affecting the ForwardOpen Handler component. The flaw exists in the CipConnMgrClass::forward_open function within cipconnectionmanager.cc, where manipulation of the product_code_ argument can cause an out-of-bounds read. This vulnerability can be exploited remotely without authentication. A patch identified by commit ea870a274bf68dfaa3f511f20e2fff6778fb7b74 has been made available to address this issue.

References

Community reviews

Loading reviews…