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,181

Total vulnerabilities in the database

Vulnerabilities for products matching "business_automation_workflow"

Found 1 matching product.

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

ibm / business_automation_workflow

52 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-13096	High	February 2, 2026 2/2/26	<= 24.0.0 == 24.0.0-if001 == 24.0.0-if002 == 24.0.0-if003 == 24.0.0-if004 == 24.0.0-if005 == 24.0.0-if006 == 24.0.0-if007 == 24.0.1 == 24.0.1-if001 == 24.0.1-if002 == 24.0.1-if004 == 24.0.1-if005 == 25.0.0 == 25.0.0-if001 == 25.0.0-if002
CVE-2025-36058	Medium	January 20, 2026 1/20/26	== 24.0.0 == 24.0.0-if001 == 24.0.0-if002 == 24.0.0-if003 == 24.0.0-if004 == 24.0.0-if005 == 24.0.0-if006 == 24.0.1 == 24.0.1-if001 == 24.0.1-if002 == 24.0.1-if004 == 24.0.1-if005 == 25.0.0 == 25.0.0-if001 == 25.0.0-if002
CVE-2025-36059	Low	January 20, 2026 1/20/26	== 24.0.0 == 24.0.0-if001 == 24.0.0-if002 == 24.0.0-if003 == 24.0.0-if004 == 24.0.0-if005 == 24.0.0-if006 == 24.0.1 == 24.0.1-if001 == 24.0.1-if002 == 24.0.1-if004 == 24.0.1-if005 == 25.0.0 == 25.0.0-if001 == 25.0.0-if002
CVE-2025-36054	Medium	November 6, 2025 11/6/25	== 24.0.0 == 24.0.0-if001 == 24.0.0-if002 == 24.0.0-if003 == 24.0.0-if004 == 24.0.0-if005 == 24.0.0-if006 == 24.0.1 == 24.0.1-if001 == 24.0.1-if002 == 24.0.1-if004 == 25.0.0 == 25.0.0-if001
CVE-2025-1495	Low	May 3, 2025 5/3/25	== 24.0.1 == 24.0.1-interim_fix_001
CVE-2024-54179	Medium	March 3, 2025 3/3/25	<= 24.0.1 == 24.0.0 == 24.0.1
CVE-2024-43188	Low	September 18, 2024 9/18/24	== 20.0.0.1 == 20.0.0.2 == 22.0.1 >= 19.0.0.1 <= 19.0.0.3 >= 21.0.1 <= 21.0.3.1 == 22.0.2 >= 18.0.0.1 <= 18.0.0.3 == 24.0.0 == 23.0.2 == 23.0.1
CVE-2024-38321	Medium	August 3, 2024 8/3/24	== 21.0.3-if011 == 21.0.3-if010 == 21.0.3-if009 == 21.0.3-if008 == 21.0.3-if007 == 21.0.3-if006 == 21.0.2 == 20.0.0.1 == 20.0.0.2 == 21.0.3-if002 == 21.0.3-if005 == 21.0.3-if012 == 21.0.3-if013 == 21.0.3-if014 == 21.0.3-if015 == 21.0.3-if016 == 22.0.1 == 22.0.2 == 21.0.3 == 21.0.3-if017 == 21.0.3-if028 == 21.0.3-if029 == 21.0.3-if030 == 21.0.3-if031 == 21.0.3-if032 == 21.0.3-if033 == 21.0.3-if034 == 23.0.1 == 23.0.2 >= 19.0.0.1 <= 19.0.0.3 >= 23.0.1 <= 23.0.2 >= 22.0.1 <= 22.0.2 >= 21.0.1 <= 21.0.3.0 >= 20.0.0.1 <= 20.0.0.2
CVE-2023-50947	Medium	February 4, 2024 2/4/24	>= 19.0.0.1 <= 19.0.0.3 == 20.0.0.1 == 20.0.0.2 >= 21.0.1 <= 21.0.3.1 == 21.0.2 == 21.0.3 == 21.0.3-if002 == 21.0.3-if005 == 21.0.3-if006 == 21.0.3-if007 == 21.0.3-if008 == 21.0.3-if009 == 21.0.3-if010 == 21.0.3-if011 == 21.0.3-if012 == 21.0.3-if013 == 21.0.3-if014 == 21.0.3-if015 == 21.0.3-if016 == 21.0.3-if017 == 21.0.3-if028 == 22.0.1 == 22.0.2 == 23.0.1 == 23.0.2
CVE-2023-24957	Medium	May 6, 2023 5/6/23	>= 19.0.0.1 <= 19.0.0.3 == 18.0.0.0 == 18.0.0.1 == 18.0.0.2 == 21.0.3-if011 == 21.0.3-if010 == 21.0.3-if009 == 21.0.3-if008 == 21.0.3-if007 == 21.0.3-if006 == 21.0.3-if005 == 21.0.3-if002 == 20.0.0.1 == 20.0.0.2 == 22.0.1 >= 21.0.1 <= 21.0.3.1 == 21.0.3-if012 == 21.0.3-if013 == 21.0.3-if014 == 22.0.2 >= 20.0.0.1 < 21.0.3 >= 22.0.1 < 22.0.2 == 22.0.2-if001 == 21.0.3-if015 == 21.0.3-if016 == 21.0.3-if017 == 21.0.3
CVE-2022-43864	High	January 26, 2023 1/26/23	== 20.0.0.1 == 20.0.0.2 == 22.0.1 >= 21.0.1 <= 21.0.3.1 == 22.0.2
CVE-2022-42435	Low	January 4, 2023 1/4/23	== 21.0.2 == 21.0.3 == 21.0.1 == 22.0.1 == 22.0.1-if001 == 22.0.1-if002 == 22.0.1-if003 == 22.0.1-if004 == 22.0.1-if005 == 21.0.3-if001 == 21.0.3-if002 == 21.0.3-if003 == 21.0.3-if004 == 21.0.3-if005 == 21.0.3-if006 == 21.0.3-if007 == 21.0.3-if008 == 21.0.3-if009 == 21.0.3-if010 == 21.0.3-if011 == 21.0.3-if012 == 21.0.3-if013 == 21.0.3-if014 == 21.0.3-if015 == 21.0.2-if001 == 21.0.2-if002 == 21.0.2-if003 == 21.0.2-if004 == 21.0.2-if005 == 21.0.2-if006 == 21.0.2-if007 == 21.0.2-if008 == 21.0.2-if009 == 21.0.2-if010 == 21.0.2-if011 == 21.0.2-if012 == 21.0.1-if001 == 21.0.1-if002 == 21.0.1-if003 == 21.0.1-if004 == 21.0.1-if005 == 21.0.1-if006 == 21.0.1-if007 == 20.0.2 == 20.0.3 == 19.0.1 == 19.0.2 == 19.0.3 == 18.0.0 == 18.0.1 == 18.0.2 == 20.0.1
CVE-2022-41735	Medium	December 7, 2022 12/7/22	== 22.0.1-if001 == 22.0.1 == 21.0.3-if011 == 21.0.3-if010 == 21.0.3-if009 == 21.0.3-if008 == 21.0.3-if007 == 21.0.3-if006 == 21.0.3-if005 == 21.0.3-if002 == 20.0.0.1 == 20.0.0.2 == 21.0.2 == 21.0.3 >= 19.0.0.1 <= 19.0.0.3 >= 21.0.1 <= 21.0.3.1 == 22.0.1-if002 == 22.0.1-if003 == 22.0.1-if004 == 21.0.3-if012 == 21.0.3-if013 == 21.0.3-if014
CVE-2022-38390	Medium	November 17, 2022 11/17/22	>= 18.0.0.0 <= 18.0.0.2 == 20.0.0.1 == 20.0.0.2 == 22.0.1 >= 19.0.0.1 <= 19.0.0.3 >= 21.0.1 <= 21.0.3.1
CVE-2022-35279	Low	November 3, 2022 11/3/22	== 22.0.1-if001 == 22.0.1 == 21.0.3-if011 == 21.0.3-if010 == 21.0.3-if009 == 21.0.3-if008 == 21.0.3-if007 == 21.0.3-if006 == 21.0.3-if005 == 21.0.3-if002 == 20.0.0.1 == 20.0.0.2 == 21.0.2 >= 18.0.0.0 <= 18.0.0.2 >= 19.0.0.0 <= 19.0.0.3 == 21.0.1 == 21.0.3
CVE-2022-22361	Medium	May 31, 2022 5/31/22	== 18.0.0.1 == 18.0.0.0 >= 19.0.0.1 <= 19.0.0.3 == 20.0.0.1 == 20.0.0.2 >= 21.0.1 <= 21.0.3
CVE-2021-39046	Low	March 18, 2022 3/18/22	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.3 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1 == 20.0.0.2 == 21.0.2
CVE-2021-38893	Medium	December 21, 2021 12/21/21	== 18.0.0.0 == 19.0.0.0 == 20.0.0.0 == 21.0.0.0
CVE-2021-38900	Medium	December 21, 2021 12/21/21	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.0 == 20.0.0.0 == 19.0.0.1 == 21.0.0.0
CVE-2021-38883	Medium	December 17, 2021 12/17/21	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.0 == 19.0.0.3 == 20.0.0.0 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1 == 20.0.0.2 == 21.0.0.0
CVE-2021-29753	Medium	November 5, 2021 11/5/21	== 18.0.0.0 == 19.0.0.0 == 21.0.0.0 == 20.0.0.0
CVE-2021-29835	Medium	October 22, 2021 10/22/21	== 18.0.0.0 == 19.0.0.0 == 20.0.0.0 == 21.0.0.0
CVE-2021-29878	Medium	October 18, 2021 10/18/21	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.0 == 19.0.0.3 == 20.0.0.0 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1 == 20.0.0.2 == 21.0.2
CVE-2021-29834	Medium	September 29, 2021 9/29/21	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.3 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1 == 20.0.0.2 == 21.0.2
CVE-2021-29751	Low	June 28, 2021 6/28/21	== 18.0.0.0 == 19.0.0.0 == 20.0.0.0
CVE-2021-29775	Medium	June 28, 2021 6/28/21	== 19.0.0.3 == 20.0.0.0
CVE-2020-4768	Medium	February 11, 2021 2/11/21	>= 18.0.0.0 <= 20.0.0.2
CVE-2020-4794	Medium	December 21, 2020 12/21/20	== 20.0.0.0 == 20.0.0.1 == 18.0.0.0 == 18.0.0.1 == 18.0.0.2 == 19.0.0.1 == 19.0.0.2 == 19.0.0.3 == 19.0.0.0 == 20.0.2.0
CVE-2020-4900	Medium	November 30, 2020 11/30/20	== 19.0.0.3
CVE-2020-4672	Medium	November 16, 2020 11/16/20	== 20.0.0.1
CVE-2020-4531	Medium	September 25, 2020 9/25/20	== 18.0.0.0 == 19.0.0.0 == 20.0.0.0
CVE-2020-4530	Medium	September 15, 2020 9/15/20	< 20.0.0.2
CVE-2020-4516	Medium	September 8, 2020 9/8/20	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.0 == 19.0.0.3 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1
CVE-2020-4698	Medium	September 8, 2020 9/8/20	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2 == 19.0.0.0 == 19.0.0.3 == 19.0.0.1 == 19.0.0.2 == 20.0.0.1
CVE-2020-4557	Medium	June 29, 2020 6/29/20	== 18.0.0.0 == 19.0.0.0 == 20.0.0.0
CVE-2020-4532	Medium	June 17, 2020 6/17/20	== 18.0.0.1 == 19.0.0.3
CVE-2020-4490	Medium	May 29, 2020 5/29/20	== 18.0.0.0 == 19.0.0.0
CVE-2020-4446	Low	May 6, 2020 5/6/20	>= 18.0.0.0 <= 18.0.0.2 >= 19.0.0.1 <= 19.0.0.3
CVE-2019-4669	Medium	February 27, 2020 2/27/20	>= 18.0.0.1 <= 19.0.0.3
CVE-2019-4426	Medium	December 13, 2019 12/13/19	== 18.0.0.0 >= 19.0.0.0 <= 19.0.0.3
CVE-2019-4149	Medium	September 5, 2019 9/5/19	>= 18.0.0.0 <= 18.0.0.2
CVE-2019-4424	High	August 20, 2019 8/20/19	>= 18.0.0.0 <= 19.0.0.2
CVE-2019-4425	Medium	August 20, 2019 8/20/19	>= 18.0.0.0 <= 19.0.0.2
CVE-2019-4410	Medium	July 1, 2019 7/1/19	>= 18.0.0.0 <= 19.0.0.1
CVE-2019-4204	Low	May 10, 2019 5/10/19	>= 18.0.0.0 <= 19.0.0.1
CVE-2019-4045	Low	April 8, 2019 4/8/19	>= 18.0.0.0 <= 18.0.0.2
CVE-2018-1885	Medium	April 8, 2019 4/8/19	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2
CVE-2018-1997	Low	April 8, 2019 4/8/19	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2
CVE-2018-1999	Low	April 8, 2019 4/8/19	== 18.0.0.1 == 18.0.0.0 == 18.0.0.2
CVE-2018-2000	Medium	April 8, 2019 4/8/19	== 18.0.0.1 == 18.0.0.0

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.