CVE-2026-19376

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-08-10. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0

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

A vulnerability has been found in Uasoft Badaso 3.0.0-alpha. This vulnerability affects the function ApiRequest::class of the file src/Routes/api.php of the component File API. The manipulation leads to permission issues. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

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
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 9, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 9, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Badaso file API allows unauthenticated file deletion and file read/download · Issue #1100 · uasoft-indonesia/badaso · GitHub

https://github.com/uasoft-indonesia/badaso/issues/1100

Vendor Advisories for CVE-2026-19376(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 54× 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.

  1. 2026-08-20 09:35 UTCGHSA enrichment
  2. 2026-08-19 22:25 UTCEG score recompute
  3. 2026-08-19 22:25 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 11:12 UTCGHSA enrichment
  6. 2026-08-18 23:57 UTCEG score recompute
  7. 2026-08-18 23:57 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 12:46 UTCGHSA enrichment
  10. 2026-08-18 00:57 UTCEG score recompute
  11. 2026-08-18 00:57 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 13:46 UTCGHSA enrichment
  14. 2026-08-17 02:36 UTCGHSA enrichment
  15. 2026-08-16 15:25 UTCEG score recompute
  16. 2026-08-16 15:25 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 04:15 UTCEG score recompute
  19. 2026-08-16 04:15 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 17:05 UTCGHSA enrichment
  22. 2026-08-15 05:55 UTCEG score recompute
  23. 2026-08-15 05:55 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 18:44 UTCGHSA enrichment
Show 29 more
  1. 2026-08-14 07:34 UTCEG score recompute
  2. 2026-08-14 07:34 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 20:23 UTCEG score recompute
  5. 2026-08-13 20:23 UTCGHSA enrichment
  6. 2026-08-13 20:20 UTCNVD updateCVSS v4 → 5.5
  7. 2026-08-13 20:02 UTCEG score recompute
  8. 2026-08-13 20:02 UTCGHSA enrichment
  9. 2026-08-13 20:01 UTCMITRE cvelistV5CVSS v4 → 6.9
  10. 2026-08-13 19:24 UTCGHSA enrichment
  11. 2026-08-13 08:13 UTCGHSA enrichment
  12. 2026-08-12 21:03 UTCGHSA enrichment
  13. 2026-08-12 19:22 UTCEG score recompute
  14. 2026-08-12 19:22 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 08:12 UTCGHSA enrichment
  17. 2026-08-11 21:01 UTCEG score recompute
  18. 2026-08-11 21:01 UTCGHSA enrichment
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 09:51 UTCEG score recompute
  21. 2026-08-11 09:51 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 22:41 UTCGHSA enrichment
  24. 2026-08-10 11:30 UTCEG score recompute
  25. 2026-08-10 11:30 UTCGHSA enrichment
  26. 2026-08-10 00:20 UTCEG score recompute
  27. 2026-08-10 00:19 UTCNVD updateCVSS v4 → 5.5
  28. 2026-08-09 23:36 UTCEG score recompute
  29. 2026-08-09 23:36 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19376?
CVE-2026-19376 is a high vulnerability published on August 9, 2026. A vulnerability has been found in Uasoft Badaso 3.0.0-alpha. This vulnerability affects the function ApiRequest::class of the file src/Routes/api.php of the component File API. The manipulation leads to permission issues. It is possible to initiate the attack remotely. The exploit has been…
When was CVE-2026-19376 disclosed?
CVE-2026-19376 was first published in the National Vulnerability Database on August 9, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19376 actively exploited?
CVE-2026-19376 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 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-19376?
CVE-2026-19376 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-19376?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19376, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19376?

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

Start Free Scan →Browse All CVEs