Code injection in the Lutece Core

Answer in brief

CVE-2026-4813 records a Unknown severity vulnerability in Code injection in the Lutece Core. The current sources do not mark it as known exploited. The current feed maps Lutece/Lutece Core (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 1, 2026Updated Sep 1, 2026Source checked Sep 1, 2026First seen by HOL Sep 1, 2026Material review Sep 1, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Lutece/Lutece Core (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Lutece/Lutece Coregeneric	>=0 <7.1.7	7.1.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for Lutece/Lutece Core.
Review the reported fix. Update Lutece/Lutece Core to 7.1.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 1, 2026

Sources and claim methodology

Source referenceincibe.es

Upstream source description

A vulnerability in the Lutece Core XSL export management module up to version 7.1.7, which allows authenticated administrators to execute code remotely. The XML/XSLT processing configuration does not enable secure processing mode (FEATURE_SECURE_PROCESSING), allowing Java extension functions to be executed from malicious XSL stylesheets. An attacker with administrator privileges can upload a manipulated XSL transformation file and trigger its execution during user export operations, resulting in the execution of arbitrary code on the server.

Quoted source text, attributed separately from HOL analysis.