CVE-2024-43405

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.4 from GitHub Security Advisory (severity: MODERATE) published 2024-09-04. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-2747 (ENISA EUVD) · GHSA-7h5p-mmpp-hgmm (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Nuclei is a vulnerability scanner powered by YAML based templates. Starting in version 3.0.0 and prior to version 3.3.2, a vulnerability in Nuclei's template signature verification system could allow an attacker to bypass the signature check and possibly execute malicious code via custom code template. The vulnerability is present in the template signature verification process, specifically in the signer package. The vulnerability stems from a discrepancy between how the signature verification process and the YAML parser handle newline characters, combined with the way multiple signatures are processed. This allows an attacker to inject malicious content into a template while maintaining a valid signature for the benign part of the template. CLI users are affected if they execute custom code templates from unverified sources. This includes templates authored by third parties or obtained from unverified repositories. SDK Users are affected if they are developers integrating Nuclei into their platforms, particularly if they permit the execution of custom code templates by end-users. The vulnerability is addressed in Nuclei v3.3.2. Users are strongly recommended to update to this version to mitigate the security risk. As an interim measure, users should refrain from using custom templates if unable to upgrade immediately. Only trusted, verified templates should be executed. Those who are unable to upgrade Nuclei should disable running custom code templates as a workaround.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 4, 2024

Last Modified

October 1, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/projectdiscovery/nuclei/v3 @ 3.3.2 (fixes >= 3.0.0, < 3.3.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/projectdiscovery/nuclei—
  • every version on: no fix on record
—
github.com/projectdiscovery/nuclei/v2—
  • every version on: no fix on record
—
github.com/projectdiscovery/nuclei/v3—
  • 3.0.0 up to 3.3.2: fixed in 3.3.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 209 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-01 08:12 UTCGHSA enrichmentGHSA-7h5p-mmpp-hgmm · GitHub severity MODERATE · GitHub CVSS 7.4
  3. 2026-11-01 08:12 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  6. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-10-27 19:31 UTCEG score recompute
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-25 17:03 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  17. 2026-10-20 19:24 UTCEG score recompute
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-10-18 07:02 UTCEG score recompute
  22. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
Show 71 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-12 17:46 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-11 21:12 UTCEG score recompute
  5. 2026-10-11 16:04 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  8. 2026-10-10 00:25 UTCOSV refresh
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  17. 2026-09-30 19:52 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  26. 2026-09-21 20:32 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  28. 2026-09-20 08:43 UTCOSV refresh
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  37. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  38. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  41. 2026-09-05 15:27 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  42. 2026-09-04 13:59 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  43. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  46. 2026-09-01 11:36 UTCOSV refresh
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  55. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  57. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  58. 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  59. 2026-08-15 11:07 UTCOSV refresh
  60. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  62. 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  65. 2026-08-09 13:45 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  66. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  69. 2026-08-05 19:16 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  70. 2026-08-04 15:08 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  71. 2026-08-04 10:36 UTCEPSS rescoreEPSS 1.1% · 62nd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-43405?
CVE-2024-43405 is a high-severity vulnerability; its CVE record was published on September 4, 2024. Nuclei is a vulnerability scanner powered by YAML based templates. Starting in version 3.0.0 and prior to version 3.3.2, a vulnerability in Nuclei's template signature verification system could allow an attacker to bypass the signature check and possibly execute malicious code via custom code…
When was the CVE record for CVE-2024-43405 published?
The CVE record for CVE-2024-43405 was published on September 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 1, 2024; the record at its source may have been updated since.
Is CVE-2024-43405 actively exploited?
CVE-2024-43405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-43405?
CVE-2024-43405 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2024-43405?
A fix for CVE-2024-43405 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-43405

Explore →

Is Your Infrastructure Affected by CVE-2024-43405?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs