The vulnerability identified as CVE-2013-2165, which affects the Red Hat JBoss RichFaces framework, has been officially added to the VulnCheck Known Exploited Vulnerabilities (KEV) catalog. This development marks a significant milestone for a security flaw that was originally disclosed over 13 years ago. According to tracking data, the vulnerability was first reserved in February 2013 and subsequently published in July of that same year.
The inclusion of this legacy vulnerability in the VulnCheck database follows reports of active exploitation surfacing on November 8, 2026. This date represents a gap of 4,857 days between the initial public disclosure of the flaw and its reported use in the wild. While the vulnerability has now been flagged by a commercial research entity, it is important to note that it does not currently appear in the CISA KEV catalog or the European Union’s ENISA vulnerability database.
The claim of active exploitation originates from a single public report linked within the VulnCheck and CIRCL datasets. Because this information relies on a solitary source, the assertion that CVE-2013-2165 is being actively targeted remains uncorroborated by other major security catalogs or government agencies. The report detailing the exploitation, titled Operation Snowball, suggests that the flaw is being leveraged in a broader context, though the specifics of these attacks have not been independently verified by external security researchers.
CVE-2013-2165 is a long-standing issue within the JBoss RichFaces component, a JavaServer Faces framework used for building web applications. Despite its age, the vulnerability’s recent appearance in threat intelligence feeds highlights the persistent risk posed by unpatched legacy software in enterprise environments. The EPSS (Exploit Prediction Scoring System) for this vulnerability is currently measured at 12.7%, placing it in the 96.4th percentile of tracked vulnerabilities.
Organizations utilizing legacy JBoss RichFaces deployments are advised to review their infrastructure for exposure to this specific CVE. While the vulnerability has remained dormant in terms of public exploitation reports for more than a decade, its sudden re-emergence underscores the importance of maintaining visibility over older, potentially forgotten components within an application stack.
As of the current reporting, Red Hat has not issued a new statement regarding this specific legacy flaw, and the primary evidence for its exploitation remains confined to the aforementioned research report. Security teams should prioritize verifying their patch levels against historical JBoss advisories to ensure that any systems still running affected versions of RichFaces are properly secured against potential unauthorized access.






