VulnerabilityPublished 27 Sep 2026Updated 6 Nov 2026

CVE-2026-96282: Red Hat Enterprise Linux 10 · Improper Link Resolution Before File Access

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Compare

Not known to be exploited · CVSS 3.1 Low.

Data as of 10 Nov 2026, 11:37 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	3.1

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 27 Sep 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.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10flatpak	Affected–	Fixed in–
Red Hat Enterprise Linux 7flatpak	Affected–	Fixed in–
Red Hat Enterprise Linux 8flatpak	Affected–	Fixed in–
Red Hat Enterprise Linux 9flatpak	Affected–	Fixed in–

AI-suggested

Red Hat advises avoiding installation of Flatpak extensions from untrusted sources. There is no indication that an official patch or fix has been released yet; therefore, users should exercise caution and only use trusted extensions. Monitor the Red Hat advisory for updates on remediation status.

Description

CVE-2026-96282 is a vulnerability in Red Hat Enterprise Linux 10 involving improper link resolution before file access in Flatpak extensions. A malicious Flatpak extension can probe the host filesystem to determine the existence of files and directories at arbitrary paths and disclose host directory listings to sandboxed applications. Additionally, unvalidated extension metadata can cause extension content to be mounted at unintended locations inside the sandbox, potentially overriding runtime directories. Exploitation requires a user to install and launch a malicious Flatpak extension with an application. No file contents are disclosed, and there is no availability impact. The vulnerability has a low CVSS score of 3.1.

Impact

The vulnerability allows an attacker to probe the host filesystem for the existence of files and directories and disclose directory listings to sandboxed applications, which may lead to limited integrity impact by mounting extension content at unintended sandbox locations and potentially overriding runtime directories. There is no confidentiality impact as file contents are not disclosed, and no availability impact is present. Exploitation requires user installation and execution of a malicious Flatpak extension.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2026, 11:57 UTC

Technical details

References

Community reviews

Related threats