How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "cxf"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/cxf/1.2.3

apache / cxf

43 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-48913	Critical	August 8, 2025 8/8/25	< 3.6.8 >= 4.0.0 < 4.0.9 >= 4.1.0 < 4.1.3
CVE-2025-48795	Medium	July 15, 2025 7/15/25	== 3.5.10 == 3.6.5 == 4.0.6 == 4.1.0
CVE-2025-23184	Medium	January 21, 2025 1/21/25	>= 4.0.0 < 4.0.6 >= 3.6.0 < 3.6.5 < 3.5.10
CVE-2024-41172	High	July 19, 2024 7/19/24	>= 4.0.0 < 4.0.5 >= 3.6.0 < 3.6.4
CVE-2024-32007	High	July 19, 2024 7/19/24	>= 4.0.0 < 4.0.5 >= 3.6.0 < 3.6.4 < 3.5.9
CVE-2024-29736	Critical	July 19, 2024 7/19/24	>= 4.0.0 < 4.0.5 >= 3.6.0 < 3.6.4 < 3.5.9
CVE-2024-28752	Critical	March 15, 2024 3/15/24	< 3.5.8 >= 3.6.0 < 3.6.3 >= 4.0.0 < 4.0.4
CVE-2022-46364	Critical	December 13, 2022 12/13/22	>= 3.5.0 < 3.5.5 < 3.4.10
CVE-2022-46363	High	December 13, 2022 12/13/22	>= 3.5.0 < 3.5.5 < 3.4.10
CVE-2021-40690	High	September 19, 2021 9/19/21	== 3.4.4
CVE-2021-30468	High	June 16, 2021 6/16/21	>= 3.4.0 < 3.4.4 < 3.3.11
CVE-2021-22696	High	April 2, 2021 4/2/21	>= 3.4.0 < 3.4.3 < 3.3.10
CVE-2020-13954	Medium	November 12, 2020 11/12/20	>= 3.4.0 < 3.4.1 < 3.3.8
CVE-2020-1954	Medium	April 1, 2020 4/1/20	>= 3.3.0 < 3.3.6 < 3.2.13
CVE-2011-2487	Medium	March 11, 2020 3/11/20	>= 2.4.0 <= 2.4.6 >= 2.5.0 <= 2.5.2
CVE-2019-12423	High	January 16, 2020 1/16/20	>= 3.3.0 < 3.3.5 < 3.2.12
CVE-2019-17573	Medium	January 16, 2020 1/16/20	>= 3.2.0 <= 3.2.12 >= 3.3.0 < 3.3.5
CVE-2019-12406	Medium	November 6, 2019 11/6/19	>= 3.3.0 < 3.3.4 < 3.2.11
CVE-2019-12419	Critical	November 6, 2019 11/6/19	>= 3.2.0 < 3.2.11 >= 3.3.0 < 3.3.4
CVE-2018-8039	Medium	July 2, 2018 7/2/18	< 3.1.16 >= 3.2.0 < 3.2.5
CVE-2017-12624	Low	November 14, 2017 11/14/17	>= 3.0.0 < 3.0.16 >= 3.1.0 < 3.1.14 >= 3.2.0 < 3.2.1
CVE-2016-8739	High	August 10, 2017 8/10/17	== 3.1.4 == 3.1.3 == 3.1.1 == 3.1.2 == 3.1.6 == 3.1.0 <= 3.0.11 == 3.1.5 == 3.1.7 == 3.1.8
CVE-2017-3156	Medium	August 10, 2017 8/10/17	== 3.1.4 == 3.1.3 == 3.1.1 == 3.1.9 == 3.1.2 == 3.1.6 == 3.1.0 <= 3.0.12 == 3.1.5 == 3.1.7 == 3.1.8
CVE-2016-6812	Low	August 10, 2017 8/10/17	== 3.1.4 == 3.1.3 == 3.1.1 == 3.1.2 == 3.1.6 == 3.1.0 <= 3.0.11 == 3.1.5 == 3.1.7 == 3.1.8
CVE-2012-0803	High	August 8, 2017 8/8/17	== 2.5.1 == 2.4.5
CVE-2017-5653	Medium	April 18, 2017 4/18/17	>= 3.0.0 <= 3.0.13 >= 3.1.0 <= 3.1.11
CVE-2017-5656	Medium	April 18, 2017 4/18/17	>= 3.0.0 < 3.0.13 >= 3.1.0 < 3.1.11
CVE-2015-5253	Low	November 18, 2015 11/18/15	< 2.7.18 >= 3.0.0 < 3.0.7 >= 3.1.0 < 3.1.3
CVE-2014-3584	Medium	October 30, 2014 10/30/14	== 2.7.3 == 2.7.5 == 2.7.6 == 3.0.0 == 2.7.0 == 2.7.4 <= 2.6.10 == 2.6.1 == 2.7.1 == 2.7.7 == 2.7.2
CVE-2014-3623	Medium	October 30, 2014 10/30/14	>= 3.0.0 < 3.0.2 >= 2.7.0 <= 2.7.13
CVE-2014-0034	Low	July 7, 2014 7/7/14	<= 2.6.11 == 2.6.0 == 2.6.1 == 2.6.10 == 2.6.2 == 2.6.3 == 2.6.4 == 2.6.5 == 2.6.6 == 2.6.7 == 2.6.8 == 2.6.9 == 2.7.0 == 2.7.1 == 2.7.2 == 2.7.3 == 2.7.4 == 2.7.5 == 2.7.6 == 2.7.7 == 2.7.8
CVE-2014-0035	Low	July 7, 2014 7/7/14	<= 2.6.12 == 2.6.8 == 2.6.0 == 2.6.2 == 2.6.9 == 2.6.5 == 2.6.10 == 2.6.6 == 2.6.3 == 2.6.4 == 2.6.11 == 2.6.1 == 2.6.7 == 2.7.3 == 2.7.5 == 2.7.6 == 2.7.9 == 2.7.0 == 2.7.4 == 2.7.1 == 2.7.8 == 2.7.7 == 2.7.2
CVE-2014-0109	Low	May 8, 2014 5/8/14	== 2.7.3 == 2.7.5 == 2.7.10 == 2.7.6 == 2.7.9 == 2.7.0 == 2.7.4 == 2.7.1 == 2.7.8 == 2.7.7 == 2.7.2 == 2.5.2 == 2.5.9 == 2.4.6 == 2.6.8 == 2.6.0 == 2.5.3 == 2.4.0 == 2.4.3 == 2.6.12 == 2.5.7 == 2.4.4 == 2.6.2 == 2.4.2 == 2.5.0 == 2.5.1 == 2.5.5 == 2.6.9 == 2.5.8 == 2.6.5 == 2.6.10 == 2.6.6 == 2.6.3 == 2.4.1 == 2.5.6 == 2.4.7 == 2.6.4 == 2.4.5 == 2.6.11 == 2.6.1 <= 2.6.13 == 2.5.4 == 2.6.7
CVE-2014-0110	Low	May 8, 2014 5/8/14	== 2.5.2 == 2.5.9 == 2.4.6 == 2.6.8 == 2.6.0 == 2.5.3 == 2.4.0 == 2.4.3 == 2.6.12 == 2.5.7 == 2.4.4 == 2.6.2 == 2.4.2 == 2.5.0 == 2.5.1 == 2.5.5 == 2.6.9 == 2.5.8 == 2.6.5 == 2.6.10 == 2.6.6 == 2.6.3 == 2.4.1 == 2.5.6 == 2.4.7 == 2.6.4 == 2.4.5 == 2.6.11 == 2.6.1 <= 2.6.13 == 2.5.4 == 2.6.7 == 2.7.3 == 2.7.5 == 2.7.10 == 2.7.6 == 2.7.9 == 2.7.0 == 2.7.4 == 2.7.1 == 2.7.8 == 2.7.7 == 2.7.2
CVE-2012-5575	Medium	August 19, 2013 8/19/13	== 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0 == 2.6.1 == 2.6.2 == 2.6.3 == 2.6.4 == 2.6.5 == 2.6.6 == 2.7.0 == 2.7.1 == 2.7.2 == 2.7.3
CVE-2013-2160	Medium	August 19, 2013 8/19/13	== 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0 == 2.6.1 == 2.6.2 == 2.6.3 == 2.6.4 == 2.6.5 == 2.6.6 == 2.7.0 == 2.7.1 == 2.7.2 == 2.7.3
CVE-2012-5633	Medium	March 12, 2013 3/12/13	<= 2.5.7 == 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 2.5.6 == 2.6.0 == 2.6.1 == 2.6.2 == 2.6.3 == 2.6.4 == 2.7.0 == 2.7.1
CVE-2013-0239	Medium	March 12, 2013 3/12/13	== 2.5.2 == 2.4.6 == 2.5.3 == 2.4.0 == 2.4.3 == 2.5.7 == 2.4.4 == 2.4.2 == 2.5.0 == 2.5.1 == 2.5.5 <= 2.5.8 == 2.4.1 == 2.5.6 == 2.4.7 == 2.4.5 == 2.5.4 == 2.6.0 == 2.6.2 == 2.6.5 == 2.6.3 == 2.6.4 == 2.6.1 == 2.7.0 == 2.7.1 == 2.7.2
CVE-2012-2378	Low	January 5, 2013 1/5/13	== 2.4.6 == 2.4.7 == 2.4.5 == 2.5.2 == 2.5.3 == 2.5.1 == 2.6.0
CVE-2012-2379	High	January 3, 2013 1/3/13	== 2.4.0 == 2.4.1 == 2.4.2 == 2.4.3 == 2.4.4 == 2.4.5 == 2.4.6 == 2.4.7 == 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.6.0
CVE-2012-5786	Medium	November 4, 2012 11/4/12	<= 2.6.17
CVE-2012-3451	Low	September 24, 2012 9/24/12	< 2.4.9 >= 2.5.0 < 2.5.5 >= 2.6.0 < 2.6.2
CVE-2010-2076	Critical	August 19, 2010 8/19/10	>= 2.0.6 < 2.0.13 >= 2.1 < 2.1.10 >= 2.2.0 < 2.2.9

org.apache.cxf / cxf

14 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-30468	High	June 16, 2021 6/16/21	>= 3.4.0 < 3.4.4 < 3.3.11
CVE-2021-22696	High	April 2, 2021 4/2/21	>= 3.4.0 < 3.4.3 < 3.3.10
CVE-2020-13954	Medium	November 12, 2020 11/12/20	< 3.3.8 >= 3.4.0 < 3.4.1
CVE-2020-1954	Medium	April 1, 2020 4/1/20	< 3.3.6
CVE-2019-12423	High	January 16, 2020 1/16/20	< 3.2.12 >= 3.3.0 < 3.3.5
CVE-2019-17573	Medium	January 16, 2020 1/16/20	< 3.2.12 >= 3.3.0 < 3.3.5
CVE-2019-12406	Medium	November 6, 2019 11/6/19	< 3.2.11 >= 3.3.0 < 3.3.4
CVE-2019-12419	Critical	November 6, 2019 11/6/19	< 3.2.11 >= 3.3.0 < 3.3.4
CVE-2018-8039	Medium	July 2, 2018 7/2/18	>= 3.2.0 < 3.2.5 < 3.1.16
CVE-2012-0803	High	August 8, 2017 8/8/17	>= 2.4.0 < 2.4.6 >= 2.5.0 < 2.5.2
CVE-2012-5633	Medium	March 12, 2013 3/12/13	< 2.5.8 >= 2.6.0 < 2.6.5 >= 2.7.0 < 2.7.2
CVE-2012-2378	Low	January 5, 2013 1/5/13	>= 2.4.5 < 2.4.8 >= 2.5.1 < 2.5.3 >= 2.6.0 < 2.6.1
CVE-2012-2379	High	January 3, 2013 1/3/13	>= 2.4.0 < 2.4.8 >= 2.5.0 < 2.5.4 >= 2.6.0 < 2.6.1
CVE-2012-3451	Low	September 24, 2012 9/24/12	< 2.4.9 >= 2.5.0 < 2.5.5 >= 2.6.0 < 2.6.2

Showing vulnerabilities for 2 products matching "cxf". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.