How severe is CVE-2025-32951?

CVE-2025-32951 has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-32951?

CVE-2025-32951 affects the following packages: io.jmix.rest:jmix-rest (Maven), io.jmix.rest:jmix-rest (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-32951?

Update io.jmix.rest:jmix-rest to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32951 is resolved across your whole dependency graph.

How do I detect CVE-2025-32951 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jmix.rest:jmix-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32951 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2025-32951 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-32951 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-32951?

CVE-2025-32951 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-32951?

CVE-2025-32951 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-32951 published, and has it been updated?

CVE-2025-32951 was published on April 22, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2025-32951 — jmix-rest

MEDIUMFix: jmix-framework/jmix@6a66aa3

CVE-2025-32951 is a medium-severity (CVSS 6.4) Cross-site Scripting (XSS) vulnerability in io.jmix.rest:jmix-rest. A fix is available for io.jmix.rest:jmix-rest — see the affected versions and patch details below.

io.jmix.rest:jmix-rest allows XSS in the /files Endpoint of the Generic REST API

Also known asGHSA-x27v-f838-jh93

Published

Apr 22, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32951.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕io.jmix.rest:jmix-rest☕io.jmix.rest:jmix-rest

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The input parameter, which consists of a file path and name, can be manipulated to return the Content-Type header with text/html if the name part ends with .html. This could allow malicious JavaScript code to be executed in the browser. For a successful attack, a malicious file needs to be uploaded beforehand.

The severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default.

Patches

The problem has been fixed in Jmix 1.6.2+ and 2.4.0+.

Workarounds

A workaround for those who are unable to upgrade: Disable Files Endpoint in Jmix Application.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jmix.rest:jmix-rest`	≥ 1.0.0&&< 1.6.2	1.6.2`io.jmix.rest:jmix-rest:1.6.2`
☕Maven	`io.jmix.rest:jmix-rest`	≥ 2.0.0&&< 2.4.0	2.4.0`io.jmix.rest:jmix-rest:2.4.0`

Affected Products

4 products · 5 configurations

Application

cuba platformhaulmont

≥ 6.2.0 && < 7.2.23

range

Application

cuba rest apihaulmont

≥ 7.1.1 && < 7.2.7

range

Application

jmix frameworkhaulmont

≥ 2.0.0 && < 2.4.0

range

Application

jpa web apihaulmont

≥ 1.0.0 && < 1.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jmix.rest:jmix-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jmix.rest:jmix-rest to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32951 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact The input parameter, which consists of a file path and name, can be manipulated to return the Content-Type header with text/html if the name part ends with .html. This could allow malicious JavaScript code to be executed in the browser. For a successful attack, a malicious file needs to be uploaded beforehand. The severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default. ### Patches

O3 Security · Impact-Aware SCA

Is CVE-2025-32951 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works