Vulnerability Database

347,064

Total vulnerabilities in the database

Vulnerabilities for products matching "netwide_assembler"

Found 1 matching product.

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

nasm / netwide_assembler

148 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium April 10, 2026 4/10/26
== 3.02-rc5
Critical April 10, 2026 4/10/26
== 3.02-rc5
High April 10, 2026 4/10/26
== 3.02-rc5
Medium August 11, 2025 8/11/25
== 2.17-rc0
Medium August 11, 2025 8/11/25
== 2.17-rc0
Low August 11, 2025 8/11/25
== 2.17-rc0
Medium August 11, 2025 8/11/25
== 2.17-rc0
Medium August 11, 2025 8/11/25
== 2.17-rc0
Medium August 22, 2023 8/22/23
== 2.16
Medium August 22, 2023 8/22/23
== 2.16
Medium August 22, 2023 8/22/23
== 2.16-rc0
Medium August 22, 2023 8/22/23
< 2.15.05
Medium August 22, 2023 8/22/23
== 2.15-rc0
Medium August 22, 2023 8/22/23
< 2.15.04
Medium August 22, 2023 8/22/23
== 2.15-rc0
Medium August 22, 2023 8/22/23
== 2.15
== 2.14.03-rc2
Medium August 22, 2023 8/22/23
== 2.14.02
High May 17, 2023 5/17/23
== 2.16.02-rc1
High March 29, 2023 3/29/23
== 2.16-rc1
< 2.16
Medium March 29, 2023 3/29/23
== 2.16-rc0
== 2.16
== 2.16-rc10
== 2.16-rc11
== 2.16-rc12
== 2.16-rc4
== 2.16-rc5
== 2.16-rc6
== 2.16-rc7
== 2.16-rc8
== 2.16-rc9
Medium March 29, 2023 3/29/23
== 2.16-rc0
== 2.16
== 2.16-rc10
== 2.16-rc11
== 2.16-rc12
== 2.16-rc4
== 2.16-rc5
== 2.16-rc6
== 2.16-rc7
== 2.16-rc8
== 2.16-rc9
Medium January 4, 2023 1/4/23
== 2.16-rc10
== 2.16-rc11
== 2.16-rc4
== 2.16-rc5
== 2.16-rc6
== 2.16-rc7
== 2.16-rc8
== 2.16-rc9
== 2.16-rc1
== 2.16-rc2
== 2.16-rc3
Medium January 4, 2023 1/4/23
== 2.16.01
== 2.16
== 2.16-rc10
== 2.16-rc11
== 2.16-rc12
== 2.16-rc4
== 2.16-rc5
== 2.16-rc6
== 2.16-rc7
== 2.16-rc8
== 2.16-rc9
Medium October 3, 2022 10/3/22
== 2.16-rc0
Medium July 26, 2022 7/26/22
== 2.16-rc0
Medium July 26, 2022 7/26/22
== 2.16-rc0
Medium December 22, 2021 12/22/21
== 2.16-rc0
Medium December 22, 2021 12/22/21
== 2.16-rc0
Low August 25, 2021 8/25/21
>= 2.15 <= 2.15.05
Critical September 4, 2020 9/4/20
== 2.15.04-rc3
Medium August 25, 2020 8/25/20
== 2.15-rc10
Medium August 25, 2020 8/25/20
== 2.15-rc10
High January 6, 2020 1/6/20
== 2.15-rc0
Medium January 4, 2020 1/4/20
== 2.14.02
Low July 24, 2019 7/24/19
>= 2.14 <= 2.14.02
Medium February 15, 2019 2/15/19
== 2.14.02
Low January 29, 2019 1/29/19
== 2.14-rc16
Low January 15, 2019 1/15/19
<= 2.14.02
Low January 15, 2019 1/15/19
<= 2.14.02
Low December 28, 2018 12/28/18
== 2.14.0-rc16
Low December 28, 2018 12/28/18
== 2.14.0-rc16
Low December 20, 2018 12/20/18
== 2.15
== 2.14.01rc5
Low November 30, 2018 11/30/18
== 12.14-rc16
Low November 12, 2018 11/12/18
== 2.14.0-rc15
Low November 12, 2018 11/12/18
== 12.14-rc16
Medium November 12, 2018 11/12/18
== 12.14-rc15
Medium November 12, 2018 11/12/18
== 12.14-rc16
Medium November 12, 2018 11/12/18
< 2.13.02
Low September 13, 2018 9/13/18
== 12.14-rc15
Medium September 6, 2018 9/6/18
== 2.14.0-rc1
== 2.14.0-rc2
== 2.14.0-rc3
== 2.14.0-rc4
== 2.14.0-rc5
== 2.14.0-rc6
== 2.14.0-rc7
== 2.14.0-rc8
== 2.14.0-rc9
== 2.14.0-rc10
== 2.14.0-rc11
== 2.14.0-rc12
== 2.14.0-rc13
== 2.14.0-rc14
<= 2.13.03
== 2.14-rc15

Frequently Asked Questions

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.