How severe is GHSA-3p3m-4x7c-p4pw?

No CVSS score has been assigned to GHSA-3p3m-4x7c-p4pw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3p3m-4x7c-p4pw?

GHSA-3p3m-4x7c-p4pw affects the following packages: mariadb (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-3p3m-4x7c-p4pw?

Update mariadb to 10.6.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3p3m-4x7c-p4pw is resolved across your whole dependency graph.

How do I detect GHSA-3p3m-4x7c-p4pw in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mariadb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3p3m-4x7c-p4pw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3p3m-4x7c-p4pw?

O3 pinpoints whether GHSA-3p3m-4x7c-p4pw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3p3m-4x7c-p4pw actively exploited in the wild?

No public exploit code has been indexed for GHSA-3p3m-4x7c-p4pw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-3p3m-4x7c-p4pw?

GHSA-3p3m-4x7c-p4pw is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3p3m-4x7c-p4pw published, and has it been updated?

GHSA-3p3m-4x7c-p4pw was published on June 13, 2026 and was last updated on August 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

GHSA-3p3m-4x7c-p4pw

GHSA-3p3m-4x7c-p4pw is a OS Command Injection vulnerability in mariadb. O3 Security confirms whether GHSA-3p3m-4x7c-p4pw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MariaDB server has unsafe parameter handling in `wsrep_notify_cmd`

Also known asBIT-mariadb-min-2026-49261BIT-mysql-client-2026-49261CVE-2026-49261

Published

Jun 13, 2026

Updated

Aug 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦mariadb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

MariaDB server is a community developed fork of MySQL server. Versions 10.6.1 through 10.6.26, 10.11.1 through 10.11.17, 11.4.1 through 11.4.11, 11.8.1 through 11.8.7, and 12.3.1 with wsrep_notify_cmd enabled would execute shell commands embedded in the name of the joiner node. This is fixed in 10.6.27, 10.11.18, 11.4.12, 11.8.8, and 12.3.2. As a workaround, anyone who cannot upgrade now should disable wsrep_notify_cmd.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`mariadb`	≥ 10.6.1&&< 10.6.27	10.6.27

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mariadb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mariadb to 10.6.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3p3m-4x7c-p4pw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3p3m-4x7c-p4pw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3p3m-4x7c-p4pw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

MariaDB server is a community developed fork of MySQL server. Versions 10.6.1 through 10.6.26, 10.11.1 through 10.11.17, 11.4.1 through 11.4.11, 11.8.1 through 11.8.7, and 12.3.1 with `wsrep_notify_cmd` enabled would execute shell commands embedded in the name of the joiner node. This is fixed in 10.6.27, 10.11.18, 11.4.12, 11.8.8, and 12.3.2. As a workaround, anyone who cannot upgrade now should disable `wsrep_notify_cmd`.

O3 Security · Impact-Aware SCA

Is GHSA-3p3m-4x7c-p4pw in your dependencies?

O3 detects GHSA-3p3m-4x7c-p4pw across Bitnami dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works