CVE-2010-1871

HIGHNVD 8.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 83%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for JBoss Expression Language (EL) expressions, which allows remote attackers to execute arbitrary code via a crafted URL. NOTE: this is only a vulnerability when the Java Security Manager is not properly configured.

CVSS v3
8.8
EG Score
9.0(high)
EPSS
99.7%
KEV
⚠ Exploited

Published

August 5, 2010

Last Modified

April 22, 2026

Advisory Details (6)

Auto-updated May 2, 2026
Patch available. Sources: redhat.
redhat Patch Available

615956 – (CVE-2010-1871) CVE-2010-1871 JBoss Seam / Seam2: Improper sanitization of parametrized JBoss EL expressions (ACE)

https://bugzilla.redhat.com/show_bug.cgi?id=615956
generic

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2010/1929

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjboss-seam2-0:2.0.2.FP-1.ep1.24.el52010-07-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 87× in last 7d / 362× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 659 total refreshes for this CVE.

  1. 2026-07-22 19:18 UTCVendor advisory
  2. 2026-07-22 19:17 UTCGHSA enrichment
  3. 2026-07-22 14:53 UTCEG score recompute
  4. 2026-07-22 14:53 UTCVendor advisory
  5. 2026-07-22 14:53 UTCGHSA enrichment
  6. 2026-07-22 14:03 UTCEPSS rescore
  7. 2026-07-22 14:03 UTCEPSS rescore
  8. 2026-07-22 10:25 UTCVendor advisory
  9. 2026-07-22 10:25 UTCGHSA enrichment
  10. 2026-07-22 06:02 UTCVendor advisory
  11. 2026-07-22 06:02 UTCGHSA enrichment
  12. 2026-07-22 01:37 UTCVendor advisory
  13. 2026-07-22 01:37 UTCGHSA enrichment
  14. 2026-07-21 21:02 UTCVendor advisory
  15. 2026-07-21 21:02 UTCGHSA enrichment
  16. 2026-07-21 16:39 UTCEG score recompute
  17. 2026-07-21 16:39 UTCVendor advisory
  18. 2026-07-21 16:39 UTCGHSA enrichment
  19. 2026-07-21 15:20 UTCEPSS rescore
  20. 2026-07-21 14:37 UTCCISA KEV update
  21. 2026-07-21 12:16 UTCVendor advisory
  22. 2026-07-21 12:16 UTCGHSA enrichment
  23. 2026-07-21 07:52 UTCVendor advisory
  24. 2026-07-21 07:52 UTCGHSA enrichment
  25. 2026-07-21 03:28 UTCVendor advisory
Show 75 more
  1. 2026-07-21 03:28 UTCGHSA enrichment
  2. 2026-07-20 23:05 UTCVendor advisory
  3. 2026-07-20 23:05 UTCGHSA enrichment
  4. 2026-07-20 18:42 UTCEG score recompute
  5. 2026-07-20 18:42 UTCVendor advisory
  6. 2026-07-20 18:42 UTCGHSA enrichment
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-20 14:19 UTCVendor advisory
  9. 2026-07-20 14:19 UTCGHSA enrichment
  10. 2026-07-20 09:56 UTCVendor advisory
  11. 2026-07-20 09:56 UTCGHSA enrichment
  12. 2026-07-20 05:34 UTCVendor advisory
  13. 2026-07-20 05:34 UTCGHSA enrichment
  14. 2026-07-20 01:10 UTCVendor advisory
  15. 2026-07-19 20:47 UTCVendor advisory
  16. 2026-07-19 20:47 UTCGHSA enrichment
  17. 2026-07-19 16:24 UTCVendor advisory
  18. 2026-07-19 16:24 UTCGHSA enrichment
  19. 2026-07-19 12:01 UTCVendor advisory
  20. 2026-07-19 12:01 UTCGHSA enrichment
  21. 2026-07-19 07:39 UTCVendor advisory
  22. 2026-07-19 07:39 UTCGHSA enrichment
  23. 2026-07-19 03:16 UTCVendor advisory
  24. 2026-07-19 03:16 UTCGHSA enrichment
  25. 2026-07-18 22:53 UTCVendor advisory
  26. 2026-07-18 22:53 UTCGHSA enrichment
  27. 2026-07-18 18:30 UTCVendor advisory
  28. 2026-07-18 18:30 UTCGHSA enrichment
  29. 2026-07-18 14:07 UTCVendor advisory
  30. 2026-07-18 14:07 UTCGHSA enrichment
  31. 2026-07-18 09:44 UTCVendor advisory
  32. 2026-07-18 09:44 UTCGHSA enrichment
  33. 2026-07-18 05:21 UTCVendor advisory
  34. 2026-07-18 05:21 UTCGHSA enrichment
  35. 2026-07-18 00:58 UTCVendor advisory
  36. 2026-07-18 00:58 UTCGHSA enrichment
  37. 2026-07-17 20:35 UTCVendor advisory
  38. 2026-07-17 20:35 UTCGHSA enrichment
  39. 2026-07-17 16:12 UTCVendor advisory
  40. 2026-07-17 16:11 UTCGHSA enrichment
  41. 2026-07-17 11:48 UTCVendor advisory
  42. 2026-07-17 11:48 UTCGHSA enrichment
  43. 2026-07-17 07:25 UTCEG score recompute
  44. 2026-07-17 07:25 UTCVendor advisory
  45. 2026-07-17 07:25 UTCGHSA enrichment
  46. 2026-07-17 03:02 UTCVendor advisory
  47. 2026-07-17 03:02 UTCGHSA enrichment
  48. 2026-07-16 22:39 UTCVendor advisory
  49. 2026-07-16 22:39 UTCGHSA enrichment
  50. 2026-07-16 18:16 UTCVendor advisory
  51. 2026-07-16 18:16 UTCGHSA enrichment
  52. 2026-07-16 17:04 UTCCISA KEV update
  53. 2026-07-16 13:49 UTCVendor advisory
  54. 2026-07-16 13:49 UTCGHSA enrichment
  55. 2026-07-16 09:25 UTCVendor advisory
  56. 2026-07-16 09:25 UTCGHSA enrichment
  57. 2026-07-16 05:02 UTCVendor advisory
  58. 2026-07-16 05:02 UTCGHSA enrichment
  59. 2026-07-16 00:38 UTCVendor advisory
  60. 2026-07-16 00:38 UTCGHSA enrichment
  61. 2026-07-15 20:16 UTCVendor advisory
  62. 2026-07-15 20:16 UTCGHSA enrichment
  63. 2026-07-15 16:54 UTCEPSS rescore
  64. 2026-07-15 16:54 UTCEPSS rescore
  65. 2026-07-15 16:49 UTCCISA KEV update
  66. 2026-07-15 15:53 UTCVendor advisory
  67. 2026-07-15 15:53 UTCGHSA enrichment
  68. 2026-07-15 15:04 UTCCISA KEV update
  69. 2026-07-15 11:29 UTCVendor advisory
  70. 2026-07-15 11:29 UTCGHSA enrichment
  71. 2026-07-15 07:04 UTCVendor advisory
  72. 2026-07-15 07:04 UTCGHSA enrichment
  73. 2026-07-15 02:42 UTCVendor advisory
  74. 2026-07-15 02:42 UTCGHSA enrichment
  75. 2026-07-14 22:18 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 Metasploit modules) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-36653✓ verified
    First seen Apr 6, 2015

    JBoss Seam 2 - Arbitrary File Upload / Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/jboss_seam_upload_exec✓ verified
    First seen Aug 5, 2010

    JBoss Seam 2 File Upload and Execute

    Open source ↗
  • Metasploitauxiliary/admin/http/jboss_seam_exec✓ verified
    First seen Jul 19, 2010

    JBoss Seam 2 Remote Command Execution

    Open source ↗

Frequently asked(6)

What is CVE-2010-1871?
CVE-2010-1871 is a high vulnerability published on August 5, 2010. JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for JBoss Expression Language (EL) expressions, which allows remote attackers to execute arbitrary code via a crafted URL. NOTE: this is only a vulnerability when…
When was CVE-2010-1871 disclosed?
CVE-2010-1871 was first published in the National Vulnerability Database on August 5, 2010, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-1871 actively exploited?
Yes. CISA added CVE-2010-1871 to the Known Exploited Vulnerabilities catalog on December 10, 2021, affecting Red Hat JBoss Seam 2. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2010-1871?
CVE-2010-1871 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2010-1871?
CVE-2010-1871 affects Red Hat JBoss Seam 2. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2010-1871?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-1871, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2010-1871

Explore →

Is Your Infrastructure Affected by CVE-2010-1871?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.