CVE-2022-3276 [High] | Command Injection in Puppetlabs-Mysql

Command injection is possible in the puppetlabs-mysql module prior to version 13.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterprise.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.72%	1.57%	+0.85%
2	2026-01-19	0.61%	0.72%	+0.11%
3	2025-12-04	—	0.61%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.72%

1.57%

+0.85%

2026-01-19

0.61%

0.72%

+0.11%

2025-12-04

—

0.61%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.4	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.7	6.0	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.4

3.1

HIGH

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.7

6.0

[email protected]

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2022-3276

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-3276 not yet assigned priority: Debian including 1 source packages (puppet-module-puppetlabs-mysql), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 2, resolved 2.	https://security-tracker.debian.org/tracker/CVE-2022-3276
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2022-3276
`ubuntu`	medium	CVE-2022-3276 medium priority: Ubuntu including 1 source packages (puppet-module-puppetlabs-mysql), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 6, needs-triage 6, released 1.	https://ubuntu.com/security/CVE-2022-3276

Affected software / configurations for CVE-2022-3276

Vendor	Product	Version	Raw CPE
puppet	puppetlabs-mysql	< 13.0.0	cpe:2.3:a:puppet:puppetlabs-mysql::::::::

References for CVE-2022-3276

URL	Tags
https://puppet.com/security/cve/CVE-2022-3276	Vendor Advisory

URL

CVE-2022-3276 | Puppetlabs-mysql Command Injection

Exploit prediction scoring system (EPSS) score for CVE-2022-3276

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3276

Weakness enumeration for CVE-2022-3276

OS Trackers for CVE-2022-3276

Affected software / configurations for CVE-2022-3276

References for CVE-2022-3276