CVE-2026-78661VulnerabilityPublished 14 Nov 2026

Loki: When coalescing adjacent text nodes

Affects lokiSource GCVE Database

Compare

Authoritative record:CVE-2026-78661· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 3.5.12-r9 soon.

Data as of 14 Nov 2026, 03:51 UTC

CVSS 3.1 base score

7.5High

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

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.5

Patch: Available – fixed in 3.5.12-r9, 1.8.0-r3, 1.9.0-r1 +2

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

Attack Vector: Network
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: 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: 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 27 Oct 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 13 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
CleanStartloki`pkg:apk/cleanstart/loki?arch=x86_64`Other threats	Affected <3.5.12-r9	Fixed in 3.5.12-r9
CleanStartloki`pkg:apk/cleanstart/loki?arch=aarch64`Other threats	Affected <3.5.12-r9	Fixed in 3.5.12-r9
CleanStartloki`pkg:apk/cleanstart/loki?arch=ppc64le`Other threats	Affected <3.5.12-r9	Fixed in 3.5.12-r9
CleanStartloki`pkg:apk/cleanstart/loki?arch=loongarch64`Other threats	Affected <3.5.12-r9	Fixed in 3.5.12-r9
CleanStartyunikorn-k8shim`pkg:apk/cleanstart/yunikorn-k8shim`Other threats	Affected <1.8.0-r3	Fixed in 1.8.0-r3
CleanStartyunikorn-k8shim`pkg:apk/cleanstart/yunikorn-k8shim`Other threats	Affected <1.9.0-r1	Fixed in 1.9.0-r1

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

AI-suggested

A patch is available and has been released in versions 3.5.12-r9, 1.8.0-r3, 1.9.0-r1, 1.11.1-r6, and 1.9.1-r7. Users should upgrade to these fixed versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-78661 is a high-severity vulnerability in the Loki software affecting multiple versions prior to their respective fixed releases. The flaw involves the handling of adjacent text nodes during operations like addText and fosterParent, where appending to an existing TextNode's Data via string concatenation can lead to a security issue. The vulnerability has been addressed in versions 3.5.12-r9, 1.8.0-r3, 1.9.0-r1, 1.11.1-r6, and 1.9.1-r7.

Impact

The vulnerability allows an unauthenticated attacker to cause a high confidentiality impact, potentially exposing sensitive data due to improper text node handling. There is no impact on integrity or availability. The flaw can be exploited remotely without user interaction or privileges, making it a significant risk if unpatched.

Summary

This vulnerability (CVE-2026-78661) affects multiple Loki package versions. It arises when adjacent text nodes are coalesced in the addText and fosterParent functions, specifically when appending to an existing TextNode's Data using string concatenation. This improper handling can lead to a security impact classified as high severity with a CVSS 3.1 base score of 7.5, indicating network attack vector, low attack complexity, no privileges or user interaction required, and high confidentiality impact without integrity or availability impact. Fixed versions have been released for all affected branches.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Nov 2026, 03:51 UTC

Technical details

References

Community reviews

Related threats