How severe is CVE-2010-2086?

No CVSS score has been assigned to CVE-2010-2086 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-2086?

CVE-2010-2086 affects the following packages: org.apache.myfaces.core:myfaces-core-module (Maven), org.apache.myfaces.core:myfaces-core-module (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-2086?

The records we use list no patched version of org.apache.myfaces.core:myfaces-core-module for CVE-2010-2086. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2010-2086 in my Maven dependencies?

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

How do I mitigate CVE-2010-2086 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-2010-2086 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-2086 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-2010-2086?

CVE-2010-2086 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th 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-2010-2086?

CVE-2010-2086 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-2010-2086 published, and has it been updated?

CVE-2010-2086 was published on May 17, 2022 and was last updated on February 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2010-2086: myfaces-core-module XSS

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.apache.myfaces.core:myfaces-core-module☕org.apache.myfaces.core:myfaces-core-module

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

Apache MyFaces 1.1.7 and 1.2.8 (All previous versions are likely vulnerable), as used in IBM WebSphere Application Server and other applications, does not properly handle an unencrypted view state, which allows remote attackers to conduct cross-site scripting (XSS) attacks or execute arbitrary Expression Language (EL) statements via vectors that involve modifying the serialized view object.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	all versions	No fix
☕Maven	`org.apache.myfaces.core:myfaces-core-module`	≥ 1.2.0	No fix

Affected Products

1 product · 2 configurations

Application

myfacesapache

2 versions

1.1.71.2.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.core:myfaces-core-module, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.myfaces.core:myfaces-core-module for CVE-2010-2086. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
JBEWS 1.0 for RHEL 4	`glassfish-jsf-0:1.2_13-2.ep5.el4`	RHSA-2010:0119

Frequently Asked Questions

Apache MyFaces 1.1.7 and 1.2.8 (All previous versions are likely vulnerable), as used in IBM WebSphere Application Server and other applications, does not properly handle an unencrypted view state, which allows remote attackers to conduct cross-site scripting (XSS) attacks or execute arbitrary Expression Language (EL) statements via vectors that involve modifying the serialized view object.

O3 Security · Impact-Aware SCA

Is CVE-2010-2086 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2010-2086 — myfaces-core-module