# CVE-2025-2901: HAL Cross Site Scripting (XSS) vulnerability of user input when storing it in a data store


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Mar 2025
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-f7jh-m6wp-jm7f

## What is CVE-2025-2901?

CVE-2025-2901 is a vulnerability in org.jboss.hal:hal-console, published on 28 Mar 2025. 

### Official description

This vulnerability is redundant to CVE-2025-23366 and CVE-2024-10234.

## Which versions are affected by CVE-2025-2901?

2 open source packages ship an affected version, including org.jboss.hal:hal-console.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.hal:hal-console` | Maven | All versions | 3.7.11.Final |
| `org.jboss.hal:hal-console` | Maven | All versions | 3.7.11.Final |

## How do I fix CVE-2025-2901?

Upgrade org.jboss.hal:hal-console to 3.7.11.Final or later.

## Is CVE-2025-2901 being exploited?

There is no known exploitation of CVE-2025-2901 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2901 and fix it if it is affected.

What it is: CVE-2025-2901 is a vulnerability in org.jboss.hal:hal-console, published on 28 Mar 2025. 
Exploitation: There is no known exploitation of CVE-2025-2901 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.hal:hal-console (Maven): affected all versions; fixed in 3.7.11.Final
- org.jboss.hal:hal-console (Maven): affected all versions; fixed in 3.7.11.Final

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2901/ (Markdown: https://insights.sbomify.com/CVE-2025-2901/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2901
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2901
- OSV: https://osv.dev/vulnerability/CVE-2025-2901

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2901/
Summaries are generated and may contain mistakes; the official description above is the record.