CVE-2026-18565 in LibreOfficeinfo

Summary

by MITRE • 11/16/2026

LibreOffice has an option, called stealth mode in earlier advisories, that stops documents from outside the trusted file locations from loading linked images and other content. The option is not on by default. With the option on, a linked background image in an HTML document was still fetched while the document was imported. In fixed versions a linked background image is checked against the option like other linked images, and is not fetched when the option blocks it.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability identified involves LibreOffice, specifically concerning its handling of external content within documents under specific security configurations known as stealth mode or trusted file location restrictions. This feature was designed to enhance user privacy by preventing applications from automatically fetching linked images and other embedded resources that originate outside a predefined set of trusted directories. The underlying technical flaw lies in the inconsistent application of these access control policies during document import processes, particularly when processing HTML-based documents. While standard image links were correctly subject to validation against the stealth mode settings, background images defined within CSS or HTML structure bypassed this check due to an oversight in the parsing logic. Consequently, even with security restrictions enabled, a malicious actor could craft an HTML document containing a linked background image hosted on an external server. When such a document is opened by a victim using LibreOffice, the application inadvertently fetches the remote resource before fully enforcing the user's privacy preferences.

From a technical perspective, this represents a failure in input validation and access control enforcement during the rendering pipeline of HTML content within office suites. The vulnerability allows for unauthorized network communication initiated by the client software without explicit user consent or awareness at the moment of document opening. This behavior undermines the intended security boundary established by the stealth mode feature, effectively creating an information leakage channel through passive data exfiltration via HTTP requests triggered by maliciously crafted files. Such mechanisms are often exploited to track users based on their IP addresses and browsing habits associated with specific documents or organizations. The flaw highlights a common challenge in complex software ecosystems where different rendering engines for various file formats may not share identical security logic paths, leading to inconsistent enforcement of global policy settings across document types like ODF versus HTML.

The operational impact of this vulnerability centers on privacy erosion and potential reconnaissance activities against the end-user or their organization. By successfully fetching external resources, an attacker can confirm the existence and activity of a target system through unique identifiers embedded in request headers or user-agent strings sent to the remote server. This capability facilitates targeted attacks by allowing adversaries to profile users based on document interaction patterns. Furthermore, it exposes network traffic analysis opportunities where observers might infer sensitive information about which documents are being accessed within an enterprise environment. Although no direct code execution occurs, the breach of confidentiality regarding user activity and location data constitutes a significant security concern for privacy-conscious individuals and organizations with strict data governance policies.

Mitigation strategies primarily involve updating to patched versions of LibreOffice where this inconsistency has been resolved by aligning background image handling with other linked content checks. Administrators should ensure that all workstations within their infrastructure are running the latest stable release containing these fixes. Additionally, users can adopt defensive measures such as configuring firewalls or proxy servers to block outbound connections from office applications unless explicitly required for legitimate business functions. Enabling strict network segmentation and monitoring egress traffic for anomalies related to document processing software can further reduce exposure risk. Awareness training regarding opening documents from untrusted sources remains critical, although technical controls must be robust enough to enforce privacy settings consistently regardless of user configuration choices or file format variations. Industry standards such as CWE-200 Information Exposure and ATT&CK technique T1567 Exfiltration Over C2 Channels provide relevant frameworks for understanding the classification and potential exploitation vectors associated with this type of vulnerability, emphasizing the need for comprehensive input validation and consistent policy enforcement across all application modules.

Responsible

Document Fdn.

Reservation

08/01/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!