CVE-2026-121191VulnerabilityPublished 10 Nov 2026

Missing Authorization Vulnerability

Source GCVE Database

Compare

Authoritative record:CVE-2026-121191· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.0.3 when convenient.

Data as of 10 Nov 2026, 14:50 UTC

CVSS 3.1 base score

6.5Medium

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.1	6.5

Patch: Available – fixed in 0.0.3

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-c3f3-fxh2-j327

What to do

Upgrade eta-remote to 0.0.3.

Affected software

Product	Affected	Fixed in
TÜBİTAK BİLGEM Software Technologies Research Instituteeta-remote	Affected >=0.0.2 <0.0.3	Fixed in 0.0.3

AI-suggested

If you cannot patch yet, restricting network access to trusted users and environments may reduce exposure. Avoid exposing eta-remote services to untrusted networks. Follow vendor guidance when it becomes available.

Description

A missing authorization vulnerability exists in TÜBİTAK BİLGEM Software Technologies Research Institute's eta-remote software versions from 0.0.2 up to but not including 0.0.3. This flaw allows unauthorized access to functionality that is not properly constrained by access control lists (ACLs). The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level with high confidentiality impact but no integrity or availability impact.

Impact

Exploitation of this vulnerability can lead to unauthorized access to sensitive functionality or data within the eta-remote software, potentially exposing confidential information. However, it does not affect data integrity or system availability. The attack requires network adjacency but no privileges or user interaction, making it moderately accessible to attackers within the network environment.

Summary

The vulnerability identified as CVE-2026-121191 affects eta-remote versions from 0.0.2 before 0.0.3 and is classified as a missing authorization issue (CWE-862). It permits an attacker with network access (attack vector: adjacent) to access functionality without proper ACL enforcement, leading to unauthorized disclosure of information (confidentiality impact: high). The vulnerability does not require privileges or user interaction and does not affect integrity or availability. No public exploits or patches are currently documented.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 14:50 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats