CVE-2026-56345

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-20. A secondary CVSS source baseline 8.1; 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

Also known asEUVD-2026-38132 (ENISA EUVD) · GHSA-jfp8-jxr2-p2jh (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists AVideo versions up to and including 29.0 as affected. No release containing a fix is confirmed on record.

AVideo through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with a filename containing an arbitrary users_id to invoke passwordless User->login() and establish an authenticated session as any user including admin. Attackers can obtain the Meet shared secret through path-traversal vulnerabilities or timing attacks against checkToken.json.php, then POST a crafted file to uploadRecordedVideo.json.php with a filename like '1-anything.mp4' to hijack admin sessions and gain full account takeover.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.5%
EPSS %ILE
39th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

June 20, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 20, 2026
No fix on record yet. Sources: github.
Web page

AVideo - Arbitrary User Session Hijacking via Meet Plugin uploadRecordedVideo Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/avideo-arbitrary-user-session-hijacking-via-meet-plugin-uploadrecordedvideo-endpoint
GitHub advisoryMentions a patch (unverified)

Meet plugin: `uploadRecordedVideo.json.php` derives `users_id` from the uploaded filename and calls passwordless `User->login()`, allowing any caller with the Meet shared secret to obtain a session as arbitrary users including admin · Advisory · WWBN/AVideo · GitHub

https://github.com/WWBN/AVideo/security/advisories/GHSA-qxvm-r42f-5p8j

Vendor Advisories for CVE-2026-56345(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
WWBN/AVideo—
  • every version through 29.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 100 of 285 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. None are among the latest 100 rows. The 185 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56345?
CVE-2026-56345 is a high-severity vulnerability; its CVE record was published on June 20, 2026. AVideo through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with…
When was CVE-2026-56345 made public?
CVE-2026-56345 was made public on May 11, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 20, 2026. EchelonGraph's copy of the record carries a last-modified date of June 23, 2026; the record at its source may have been updated since.
Is CVE-2026-56345 actively exploited?
CVE-2026-56345 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56345?
CVE-2026-56345 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56345?
No fix for CVE-2026-56345 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 CVE record's CNA (VulnCheck) lists AVideo versions up to and including 29.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-56345 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56345

Explore →

Is Your Infrastructure Affected by CVE-2026-56345?

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

Book a Demo →Browse All CVEs