External risk intelligence

Lutece Core XSL Export RCE via Malicious Stylesheets

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-4813

The vulnerability requires authenticated administrator privileges to execute the malicious XSL transformation. While the application may be network-reachable, the requirement for high-level administrative access significantly limits the exposed attack surface, as such interfaces are typically restricted to authorized internal personnel rather than being exposed to the public internet.

Code Injection

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in the Lutece Core module that could allow a privileged user to execute arbitrary code on the server. This occurs when a specially crafted XSL transformation file is uploaded and processed, bypassing security configurations. The main concern at this time is confirming if this specific module is in use and potentially exposed.

  • Admins can upload malicious files to run code.
  • Critical for Lutece Core, if deployed and exposed.
  • Confirm relevance and investigate potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with administrator privileges can exploit this vulnerability by uploading a malicious XSL stylesheet. When this stylesheet is processed during user export operations, it can execute arbitrary code on the server due to the insecure XML/XSLT processing configuration.

  • Authenticated administrator access is required.
  • Uploading a malicious XSL stylesheet triggers the vulnerability.
  • Risk includes arbitrary code execution on the server.

Live Threat

Current exploitation, exposure, and threat context

Authenticated administrators could face remote code execution when processing user exports via manipulated XSL stylesheets. This could impact server-side operations when specific processing configurations are not enabled.

  • Server code execution
  • Malicious XSL stylesheet upload
  • Arbitrary code execution on server

Operational Fix

Recommended remediation, mitigation, and detection steps

The Lutece Core administrators responsible for the application's security and maintenance are likely the first point of contact. Initial efforts should focus on identifying all instances of the affected Lutece Core software, determining their exposure, and confirming business criticality to prioritize remediation.

  • Application owners should own the issue.
  • Verify administrator access and export functions.
  • Plan remediation during a maintenance window.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Lutece Core software?

Lutece Core is a modular Java-based framework used for building web applications and content management systems. The specific module affected here handles XSL exports, which allow the system to transform and format data—such as user lists or records—into various document types. It is commonly deployed by organizations to manage and process structured information.

What does CVE-2026-4813 mean in simple terms?

This vulnerability is classified as CWE-94: Improper Control of Generation of Code. Because the XSLT processor does not have secure processing mode enabled, it mistakenly treats commands embedded within a stylesheet as legitimate instructions for the server to run. By uploading a manipulated XSL file, an authorized user can trick the server into executing arbitrary code.

How is this vulnerability triggered?

An attacker must have administrative privileges to upload and initiate the processing of a malicious XSL stylesheet within the export management module. Simply navigating to the application or viewing public pages does not trigger the bug. The code execution only occurs when the server processes the specific, attacker-provided stylesheet during an export operation.

Is my server at risk if it is not internet-facing?

Halo Surface Signal indicates that while the application may be network-reachable, the requirement for high-level administrative access significantly limits the potential attack surface. Because this exploit relies on an authenticated administrator, it is less likely to be accessible to anonymous internet users; however, internal account compromise still remains a relevant security concern.

What should I do if I run Lutece Core?

Begin by auditing your environment to locate all active instances of Lutece Core and determine if the XSL export module is currently in use. Verify who holds administrative credentials for these systems and review recent logs for unauthorized file uploads. Coordinate with your application maintenance team to schedule updates or configuration changes during your next planned window.

References