Security readout for executives and security teams
Plain-English summary
CVE-2026-38165 is a critical flaw in XDocReport’s Velocity template configuration. Applications that process attacker-controlled template expressions with affected versions could allow remote, unauthenticated attackers to run code, potentially compromising data, altering systems, or disrupting services.
Executive priority
Treat internet-facing or externally supplied document-processing deployments as an immediate priority. Identify ownership and exposure now, contain reachable instances, and expedite a vendor-confirmed remediation. Internal deployments remain urgent when untrusted users or systems can submit content.
Technical view
XDocReport versions 0.9.2 through 2.2.0 are reported vulnerable to server-side template injection. A crafted Velocity expression can result in arbitrary code execution. The CVSS 3.1 score is 9.8, reflecting network reachability, low complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where an application uses XDocReport 0.9.2–2.2.0 and permits untrusted document, template, or expression content to reach Velocity processing. The supplied record contains no CPEs, so automated asset matching may miss affected deployments.
Exploitation context
The source bundle says this CVE is not in KEV and provides no evidence of active exploitation. Public technical research and a CVE-specific repository are referenced, indicating public awareness, but they do not establish malicious exploitation in the wild.
Researcher notes
The record identifies CWE-94 and arbitrary code execution through crafted Velocity expressions. However, affected-product metadata is incomplete, no CPEs are supplied, and the bundle does not name a fixed version. Reachability depends on application data flow, which must be validated locally.
Mitigation direction
- Inventory applications and services using XDocReport versions 0.9.2 through 2.2.0.
- Prevent untrusted content from reaching Velocity template evaluation until remediation is confirmed.
- Restrict network access and isolate affected document-processing services where operationally feasible.
- Review upstream guidance and pull request 723 for a confirmed fix or safe upgrade path.
- Apply and test a vendor-confirmed remediation as soon as it becomes available.
Validation and detection
- Confirm deployed XDocReport versions using dependency inventories, build manifests, and software composition analysis.
- Trace whether external documents, templates, or expressions can reach Velocity processing.
- Review application controls for authentication, input trust boundaries, and document-processing isolation.
- Examine relevant application and host telemetry for unexpected activity associated with template processing.
- Retest affected workflows after remediation without using production systems or sensitive data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-38165 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/opensagres/xdocreportCVE reference, mitre
- https://hackmd.io/@cuongnh/SyPn-XF0llCVE reference, mitre
- https://hackmd.io/@cuongnh/H1sB1RIy-gCVE reference, mitre
- https://github.com/opensagres/xdocreport/pull/723CVE reference, mitre
- https://github.com/AT190510-Cuong/CVE-2026-38165-SSTI-CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.