Skip to main content
VulnerabilityPublished

CVE-2026-92886: TÜBİTAK BİLGEM Software Technologies Research Institute eta-register · Missing Authorization

Affects TÜBİTAK BİLGEM Software Technologies Research Institute eta-registerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 2.0.9 soon.

Data as of 2 Nov 2026, 13:13 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (TR-CERT)CVSS 3.17.8
Patch
Available – fixed in 2.0.9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade TÜBİTAK BİLGEM Software Technologies Research Institute eta-register to 2.0.9.

Affected software

ProductAffectedFixed in
TÜBİTAK BİLGEM Software Technologies Research Instituteeta-registerAffected
  • >=2.0.8 <2.0.9
Fixed in
  • 2.0.9

AI-suggested

Users should upgrade eta-register to version 2.0.9 or later, where this vulnerability has been fixed. No other mitigation actions are indicated by the vendor advisory.

Description

CVE-2026-92886 is a Missing Authorization vulnerability in the eta-register software developed by TÜBİTAK BİLGEM Software Technologies Research Institute. It affects versions from 2.0.8 up to but not including 2.0.9. This flaw allows privilege escalation, potentially enabling an attacker with limited privileges to gain higher-level access. The issue has been fixed in version 2.0.9.

References

Community reviews

Loading reviews…