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.

357,869

Total vulnerabilities in the database

Vulnerabilities for products matching "fuse"

Found 5 matching products. Filters apply to all results.

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

fuse / fuse

128 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-0541	Low	September 2, 2011 9/2/11	== 2.4.2 == 2.6.0 == 2.4.1 == 2.2 == 2.6.5 == 2.7.0 == 2.7.4 == 2.3.0 == 2.4.0 == 2.6.3 == 2.5.3 == 2.3-pre == 2.0-pre1 == 2.8.1 == 2.2.1 == 2.5.1 == 2.7.1 == 2.8.2 == 2.7.2 == 2.1 == 2.8.0 == 2.5.2 <= 2.8.5 == 1.9 == 2.7.5 == 2.7.6 == 2.5.0 == 2.6.1 == 2.8.4 == 2.8.3 == 2.0-pre0 == 2.7.3 == 2.3-rc1
CVE-2011-0542	Low	September 2, 2011 9/2/11	== 2.4.2 == 2.6.0 == 2.4.1 == 2.2 == 2.6.5 == 2.7.0 == 2.7.4 == 2.3.0 == 2.4.0 == 2.6.3 == 2.5.3 == 2.3-pre == 2.0-pre1 == 2.8.1 == 2.2.1 == 2.5.1 == 2.7.1 == 2.8.2 == 2.7.2 == 2.1 == 2.8.0 == 2.5.2 <= 2.8.5 == 1.9 == 2.7.5 == 2.7.6 == 2.5.0 == 2.6.1 == 2.8.4 == 2.8.3 == 2.0-pre0 == 2.7.3 == 2.3-rc1
CVE-2011-0543	Low	September 2, 2011 9/2/11	== 2.4.2 == 2.6.0 == 2.4.1 == 2.2 == 2.6.5 == 2.7.0 == 2.7.4 == 2.3.0 == 2.4.0 == 2.6.3 == 2.5.3 == 2.3-pre == 2.0-pre1 == 2.8.1 == 2.2.1 == 2.5.1 == 2.7.1 == 2.8.2 == 2.7.2 == 2.1 == 2.8.0 == 2.5.2 <= 2.8.5 == 1.9 == 2.7.5 == 2.7.6 == 2.5.0 == 2.6.1 == 2.8.4 == 2.8.3 == 2.0-pre0 == 2.7.3 == 2.3-rc1
CVE-2010-0789	Low	March 2, 2010 3/2/10	== 2.4.2 == 2.6.0 == 2.4.1 == 2.2 == 2.6.5 == 2.7.0 == 2.7.4 == 2.3.0 == 2.4.0 == 2.6.3 == 2.5.3 == 2.3-pre == 2.0-pre1 == 2.2.1 == 2.5.1 == 2.7.1 == 2.7.2 == 2.1 == 2.5.2 == 1.9 == 2.5.0 == 2.6.1 == 2.0-pre0 == 2.7.3 == 2.3-rc1
CVE-2005-1858	Low	June 3, 2005 6/3/05	== 2.2 == 2.3_rc1 == 2.2.1 == 2.3_pre

miklos_szeredi / fuse

5 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2005-3531	Low		November 23, 2005 11/23/05	== 2.3_rc1 == 2.2 == 2.2.1 == 2.3.0 == 2.4.0

fuse_project / fuse

3 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2018-10906	Low		July 24, 2018 7/24/18	>= 3.0 < 3.2.5 < 2.9.8
CVE-2015-3202	Low		July 2, 2015 7/2/15	<= 2.9.2

debian / fuse

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2016-1233	High		January 26, 2016 1/26/16	<= 2.9.3-14

redhat / fuse

28 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-28367	High	March 27, 2026 3/27/26	== 7.0.0
CVE-2026-28368	High	March 27, 2026 3/27/26	== 7.0.0
CVE-2026-28369	High	March 27, 2026 3/27/26	== 7.0.0
CVE-2025-57849	Medium	March 13, 2026 3/13/26	== 7.0.0
CVE-2025-12543	Critical	January 7, 2026 1/7/26	== 7.0.0
CVE-2025-9784	High	September 2, 2025 9/2/25	== 7.0.0
CVE-2024-1635	High	February 20, 2024 2/20/24	== 1.0
CVE-2023-1108	High	September 14, 2023 9/14/23	== 1.0.0
CVE-2021-3690	High	July 15, 2022 7/15/22	== 1.0
CVE-2021-4178	Medium	July 15, 2022 7/15/22	== 7.11
CVE-2021-3597	Medium	May 25, 2022 5/25/22	== 1.0
CVE-2020-25689	Medium	May 24, 2022 5/24/22	== 6.0.0
CVE-2019-10174	High	May 24, 2022 5/24/22	== 1.0
CVE-2016-4437	Critical	May 14, 2022 5/14/22	== 1.0
CVE-2017-12617	High	May 14, 2022 5/14/22	== 1.0
CVE-2019-0204	High	May 13, 2022 5/13/22	== 7.5.0
CVE-2019-14900	Medium	February 10, 2022 2/10/22	< 7.8.0
CVE-2020-10688	Medium	June 15, 2021 6/15/21	== 1.0
CVE-2020-10719	Medium	April 30, 2021 4/30/21	== 1.0
CVE-2017-7957	High	June 30, 2020 6/30/20	== 1.0
CVE-2019-10219	Medium	January 8, 2020 1/8/20	== 1.0
CVE-2017-5645	Critical	January 6, 2020 1/6/20	== 1.0
CVE-2019-14860	Medium	November 8, 2019 11/8/19	< 7.5.0
CVE-2019-0201	Medium	May 29, 2019 5/29/19	== 1.0.0
CVE-2018-1270	Critical	October 17, 2018 10/17/18	== 1.0.0
CVE-2018-1258	High	October 17, 2018 10/17/18	== 7.3.0
CVE-2018-1199	Medium	October 17, 2018 10/17/18	== 1.0
CVE-2015-1427	High	February 17, 2015 2/17/15	== 1.0.0

Showing vulnerabilities for 5 products matching "fuse". 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.