What is the CVSS score of CVE-2026-27005?

CVE-2026-27005 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2026-27005?

Yes, a public proof-of-concept exploit is available for CVE-2026-27005. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2026-27005?

Within 24 hours: Immediately identify all Chartbrew instances in production and their version numbers; isolate affected instances from external network access if possible; enable verbose logging on connected databases. Within 7 days: Upgrade to Chartbrew 4.8.3 or later; audit database access logs for suspicious SQL activity; conduct data exposure assessment for accessed databases. Within 30 days: Perform full security review of Chartbrew deployment; implement network segmentation to restrict database access; establish monitoring for SQL injection patterns.

Chartbrew CVE-2026-27005

CRITICAL

SQL Injection (CWE-89)

2026-03-06 security-advisories@github.com

PostgreSQL MySQL Chartbrew Depomo

9.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send HTTP request to Chartbrew query endpoint
Exploit

Inject malicious SQL into unvalidated query parameter
Execution

Execute arbitrary SQL against connected database
Impact

Exfiltrate, modify, or delete sensitive data

Vulnerability Assessment

Weakness	CWE CWE-89 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Parameterized queries, prepared statements MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	No special conditions — remote unauthenticated exploitation against Chartbrew instances prior to version 4.8.3 with connected MySQL or PostgreSQL databases. No authentication required; default configurations vulnerable.
Impact	CVSS 9.8.
Exploit ScenarioDerived	SQL injection to access connected databases.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

SQL injection in Chartbrew before 4.8.3. PoC available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:06 CVSS 9.8

SQLi in Chartbrew data visualization.

RemediationAI

Update.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-89.

Know when Chartbrew gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 10, 2026 - 14:04 vuln.today

Public exploit code

CVE Published

Mar 06, 2026 - 05:16 nvd

CRITICAL 9.8

DescriptionGitHub Advisory

Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to version 4.8.3, an unauthenticated attacker can inject arbitrary SQL into queries executed against databases connected to Chartbrew (MySQL, PostgreSQL). This allows reading, modifying, or deleting data in those databases depending on the database user's privileges. This issue has been patched in version 4.8.3.

Executive ViewAI

Why It Matters

Chartbrew versions prior to 4.8.3 contain a critical SQL injection vulnerability that allows unauthenticated attackers to directly access and manipulate data in connected databases without valid credentials. Any organization using Chartbrew to manage business intelligence, reporting, or analytics faces immediate risk of unauthorized data access, exfiltration, and potential data destruction.

Business Impact: Severe

Compensating Controls

Until patching is completed: Deploy Web Application Firewall (WAF) rules to block common SQL injection patterns in Chartbrew requests; restrict Chartbrew network access to known internal IPs only via firewall/network segmentation; disable public-facing Chartbrew instances or place behind VPN/authentication gateway; revoke or rotate database credentials used by Chartbrew; implement database-level query monitoring and alerting for anomalous SQL patterns; consider disabling Chartbrew entirely until patch can be applied.

Threat Intelligence Overview

EPSS Score

0.2%

Top 64% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.2%

Patch available No

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.