CVE-2024-7883

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2024-10-31. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When using Arm Cortex-M Security Extensions (CMSE), Secure stack contents can be leaked to Non-secure state via floating-point registers when a Secure to Non-secure function call is made that returns a floating-point value and when this is the first use of floating-point since entering Secure state. This allows an attacker to read a limited quantity of Secure stack contents with an impact on confidentiality. This issue is specific to code generated using LLVM-based compilers.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

October 31, 2024

Last Modified

December 23, 2025

References (1)

Affected Packages

(10 across 4 ecosystems)
Debian:12(4)
PackageVulnerable rangeFixed inDependents
llvm-toolchain-141:14.0.6-12 ... 1:14.0.6-20 (11 versions)——
llvm-toolchain-151:15.0.6-4 ... 1:15.0.7-9 (24 versions)——
llvm-toolchain-161:16.0.0-1~exp1 ... 1:16.0.6-9 (52 versions)——
llvm-toolchain-191:19.1.0-1 ... 1:19.1.7-9 (54 versions)——
Debian:13(3)
PackageVulnerable rangeFixed inDependents
llvm-toolchain-171:17.0.6-22, 1:17.0.6-23——
llvm-toolchain-181:18.1.8-18, 1:18.1.8-20——
llvm-toolchain-191:19.1.7-10 ... 1:19.1.7-9 (21 versions)——
Debian:11(2)
PackageVulnerable rangeFixed inDependents
llvm-toolchain-161:16.0.0-1~exp1 ... 1:16.0.6-9 (52 versions)——
llvm-toolchain-191:19.1.0-1 ... 1:19.1.7-9 (54 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
llvm-toolchain-191:19.1.7-10 ... 1:19.1.7-9 (15 versions)1:19.1.7-16—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 165 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-7883?
CVE-2024-7883 is a low vulnerability published on October 31, 2024. When using Arm Cortex-M Security Extensions (CMSE), Secure stack contents can be leaked to Non-secure state via floating-point registers when a Secure to Non-secure function call is made that returns a floating-point value and when this is the first use of floating-point since entering Secure…
When was CVE-2024-7883 disclosed?
CVE-2024-7883 was first published in the National Vulnerability Database on October 31, 2024, with the most recent update on December 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-7883 actively exploited?
CVE-2024-7883 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2024-7883?
CVE-2024-7883 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2024-7883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-7883, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-7883?

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

Start Free Scan →Browse All CVEs