CVE-2026-59247VulnerabilityPublished 6 Aug 2026Updated 10 Nov 2026

SUSE · gleam-1.18.1-1.1 on GA media

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-59247· High 7.6

Not known to be exploited · CVSS 7.6 High · fixed in SUSE package updates : patch SUSE gleam soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score

7.6High

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (EEF)	CVSS 4.0	7.6

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.18.0, v1.18.0-scratch, v1.18.0-node-slim +9

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jul 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Gleamgleam	Affected >=0.18.0-rc1 <1.18.0	Fixed in 1.18.0
Gleamgleam-lang/gleam	Affected >=0.18.0-rc1-elixir <1.18.0-elixir >=0.18.0-rc1-erlang <1.18.0-erlang >=0.18.0-rc1-node <1.18.0-node >=0.18.0-rc1-node-slim <1.18.0-node-slim >=0.18.0-rc1-elixir-slim <1.18.0-elixir-slim >=0.18.0-rc1-erlang-slim <1.18.0-erlang-slim >=0.18.0-rc1-erlang-alpine <1.18.0-erlang-alpine >=0.18.0-rc1-elixir-alpine <1.18.0-elixir-alpine >=0.18.0-rc1-node-alpine <1.18.0-node-alpine >=0.18.0-rc1-scratch <1.18.0-scratch	Fixed in v1.18.0-scratch v1.18.0-node-slim v1.18.0-node-alpine v1.18.0-node v1.18.0-erlang-slim v1.18.0-erlang-alpine v1.18.0-erlang v1.18.0-elixir-slim v1.18.0-elixir-alpine v1.18.0-elixir
Gleamgleam-lang/gleam	Affected ≥ 8447b78cc844ff4aec44eea23dbd68d1fea11f11, < c9c0d48c123c8abae6db8dd61b25ccb427ed3d35	Fixed in c9c0d48c123c8abae6db8dd61b25ccb427ed3d35

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

These are all security issues fixed in the gleam-1.18.1-1.1 package on the GA media of openSUSE Tumbleweed.

References

Community reviews

Loading reviews…