CVE-2026-19198

HIGHPre-NVD 8.78.7
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 4 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: Elevated riskExposed: 0

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

Akaunting 3.1.21 contains an authenticated improper authorization vulnerability in the common BulkActions dispatcher.This issue affects Akaunting: 3.1.21.

CVSS v3
8.7
EG Score
8.7(low)
EG Risk
55(Track*)
EG Risk 55/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
Severity87% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github_release.
github_release Patch Available

3.2.1

Patch available: akaunting/akaunting 3.2.1

https://github.com/akaunting/akaunting/releases/tag/3.2.1
generic

GitHub - akaunting/akaunting: Online Accounting Software · GitHub

https://github.com/akaunting/akaunting
generic

Akaunting 3.1.21 - Improper authorization in BulkActions handle dispatch | Fluid Attacks

https://fluidattacks.com/advisories/badbo

Vendor Advisories for CVE-2026-19198(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 8× in last 7d / 8× 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 22:55 UTCEPSS rescore
  2. 2026-08-20 22:22 UTCGHSA enrichment
  3. 2026-08-20 09:22 UTCGHSA enrichment
  4. 2026-08-19 20:22 UTCEG score recompute
  5. 2026-08-19 19:44 UTCEG score recompute
  6. 2026-08-19 19:19 UTCEG score recompute
  7. 2026-08-19 19:10 UTCEG score recompute
  8. 2026-08-19 19:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19198?
CVE-2026-19198 is a high vulnerability published on August 19, 2026. Akaunting 3.1.21 contains an authenticated improper authorization vulnerability in the common BulkActions dispatcher.This issue affects Akaunting: 3.1.21.
When was CVE-2026-19198 disclosed?
CVE-2026-19198 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19198 actively exploited?
CVE-2026-19198 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 84.9% of all scored CVEs.
What is the CVSS score of CVE-2026-19198?
CVE-2026-19198 has a CVSS v3 base score of 8.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-19198?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19198, 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-19198

Explore →

Is Your Infrastructure Affected by CVE-2026-19198?

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

Start Free Scan →Browse All CVEs