Skip to content
CVE-2026-108963: High-Risk Remote Code Execution Vulnerability in Databasement

CVE-2026-108963: High-Risk Remote Code Execution Vulnerability in Databasement

First seen 12 Oct 2026, 01:58 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 12, 2026 at 03:29 UTC
  • •CVE-2026-108963 allows remote code execution in databasement versions before 1.8.2.
  • •The vulnerability has a CVSS score of 8.8, classified as high severity.
  • •No public proof-of-concept or confirmed exploitation has been reported yet.

CVE-2026-108963, published on October 11, 2026, reveals a high-severity vulnerability in databasement versions prior to 1.8.2, allowing remote code execution via argument injection. Authenticated users can exploit this flaw by specifying arbitrary database names in commands like mariadb-dump, enabling file writes to the server filesystem. The vulnerability has a CVSS score of 8.8, indicating significant risk. Currently, there is no public proof-of-concept or confirmed exploitation reported. Users are advised to upgrade to version 1.8.2 or later and implement input validation to mitigate risks. The vulnerability affects any authenticated user over the network, potentially leading to unauthorized code execution on the server. Security patches are available, and organizations are urged to review their server configurations and access controls.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-11
CVE-2026-108963 published
CVE-2026-108963 was disclosed, detailing a remote code execution vulnerability in databasement before version 1.8.2.
Feedly
Recent
Patch released
A security patch for databasement was made available in version 1.8.2 to address the vulnerability.
TheHackerWire

More articles in this cluster (4)

Following this threat?

Track CVE-2026-108963 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
Databasement versions prior to 1.8.2 are affected by this vulnerability.
Is there a patch available?
Yes, a patch has been released in version 1.8.2 to mitigate the vulnerability.
What should organizations do?
Organizations should upgrade to version 1.8.2 or later and implement input validation on database name parameters.