CVE-2026-33963

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-14. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

An issue was discovered in camera in Samsung Mobile Processor Exynos 1330, 1380, 1480, 2400, 1580, 2500, 2600, and 1680. A stack-based buffer overflow occurs when a malformed message is sent to the camera driver, causing a denial of service.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 14, 2026

Last Modified

September 22, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
No fix on record yet.
Web page

CVE-2026-33963 | Support | Samsung Semiconductor Global

https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2026-33963/
Web page

Product Security Update | Support | Samsung Semiconductor Global

https://semiconductor.samsung.com/support/quality-support/product-security-updates/

Vendor Advisories for CVE-2026-33963(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 107× 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 99 of 107 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 8 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33963?
CVE-2026-33963 is a high-severity vulnerability; its CVE record was published on September 14, 2026. An issue was discovered in camera in Samsung Mobile Processor Exynos 1330, 1380, 1480, 2400, 1580, 2500, 2600, and 1680. A stack-based buffer overflow occurs when a malformed message is sent to the camera driver, causing a denial of service.
When was the CVE record for CVE-2026-33963 published?
The CVE record for CVE-2026-33963 was published on September 14, 2026. 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 September 22, 2026; the record at its source may have been updated since.
Is CVE-2026-33963 actively exploited?
CVE-2026-33963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33963?
CVE-2026-33963 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33963?
No fix for CVE-2026-33963 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-33963 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33963

Explore →

Is Your Infrastructure Affected by CVE-2026-33963?

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

Book a Demo →Browse All CVEs