# CVE-2025-12799: Jastow: jastow cross-site scripting attack due to unsanitized uri > Attackers can execute arbitrary scripts in user browsers via unsanitized URIs in JBoss EAP when specific combined configurations are enabled. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Jul 2026 - **Updated:** 29 Jul 2026 - **Also known as:** GHSA-rfhw-2486-47r9, RHSA-2026:36342, RHSA-2026:36343, RHSA-2026:36344 ## What is CVE-2025-12799? CVE-2025-12799 is a medium-severity cross-site scripting vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in Jastow. Jastow is vulnerable to Cross-Site Scripting (XSS) attack. If using a set of combined configuration to allow unescaped characters in URL with embedded Undertow and Jastow, a server might be vulnerable to improper input handling. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-12799? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `eap8` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:1-9.el10eap | | `eap8-activemq-artemis` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-cli` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-commons` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-core-client` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-dto` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-hornetq-protocol` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-hqclient-protocol` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-jakarta-client` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-jakarta-ra` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-jakarta-server` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-jakarta-service-extensions` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-jdbc-store` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-journal` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-native` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 1:2.0.0-2.redhat_00005.1.el10eap | | `eap8-activemq-artemis-selector` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-activemq-artemis-server` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.40.0-7.redhat_00015.1.el10eap | | `eap8-aesh-extensions` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:1.8.0-2.redhat_00001.1.el10eap | | `eap8-aesh-readline` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.4.0-1.redhat_00002.1.el10eap | | `eap8-agroal` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.3.0-1.redhat_00001.1.el10eap | | `eap8-agroal-api` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.3.0-1.redhat_00001.1.el10eap | | `eap8-agroal-narayana` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.3.0-1.redhat_00001.1.el10eap | | `eap8-agroal-pool` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.3.0-1.redhat_00001.1.el10eap | | `eap8-angus` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.0.5-1.redhat_00001.1.el10eap | | `eap8-angus-activation` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.0.3-1.redhat_00001.1.el10eap | | `eap8-angus-mail` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.0.5-1.redhat_00001.1.el10eap | | `eap8-antlr4` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.13.2-1.redhat_00001.1.el10eap | | `eap8-antlr4-runtime` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.13.2-1.redhat_00001.1.el10eap | | `eap8-apache-commons-beanutils` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:1.11.0-1.redhat_00001.1.el10eap | | `eap8-apache-commons-cli` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:1.9.0-1.redhat_00001.1.el10eap | | `eap8-apache-commons-codec` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:1.17.2-1.redhat_00001.1.el10eap | | `eap8-apache-commons-collections` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:3.2.2-28.redhat_2.1.el10eap | | `eap8-apache-commons-io` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:2.16.1-2.redhat_00002.1.el10eap | | `eap8-apache-commons-lang` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:3.18.0-2.redhat_00003.1.el10eap | | `eap8-apache-cxf` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.0.10-3.redhat_00001.1.el10eap | | `eap8-apache-cxf-rt` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.0.10-3.redhat_00001.1.el10eap | | `eap8-apache-cxf-services` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.0.10-3.redhat_00001.1.el10eap | | `eap8-apache-cxf-tools` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.0.10-3.redhat_00001.1.el10eap | | `eap8-apache-cxf-xjc-utils` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:4.1.0-1.redhat_00001.1.el10eap | | `eap8-apache-mime4j` | Red Hat:jboss_enterprise_application_platform:8.1::el10 | All versions | 0:0.8.12-1.redhat_00001.1.el10eap | ## How do I fix CVE-2025-12799? Apply the vendor's patch. ## Is CVE-2025-12799 being exploited? There is no known exploitation of CVE-2025-12799 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-12799 and fix it if it is affected. What it is: CVE-2025-12799 is a medium-severity cross-site scripting vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-12799 in the wild and no public exploit code. Affected product: Red Hat JBoss Enterprise Application Platform 7. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-12799/ (Markdown: https://insights.sbomify.com/CVE-2025-12799/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12799 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12799 - OSV: https://osv.dev/vulnerability/CVE-2025-12799 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-12799/ Summaries are generated and may contain mistakes; the official description above is the record.