GHSA-c46w-gr7f-jm2p CVE-2025-22239 PYSEC-2026-1897

Salt vulnerable to arbitrary event injection

High PyPI

Severity: 8.1 / 10; High · CVSS 3.1
Exploit chance (EPSS): 0.18%; Chance of exploitation in the next 30 days. Higher than 7.70% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-285 Improper Authorization
Fix: 3006.12; Upgrade salt to this version or later

Description

Arbitrary event injection on Salt Master. The master's "_minion_event" method can be used by and authorized minion to send arbitrary events onto the master's event bus.

Affected versions

PyPI

Package	Vulnerable	Fixed in
salt	`>= 3006.0rc1, < 3006.12`	`3006.12`
salt	`>= 3007.0rc1, < 3007.4`	`3007.4`
salt	`>= 3006.0rc1, < 3006.12` `>= 3007.0rc1, < 3007.4`	`3006.12` `3007.4`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

salt PyPI → `3006.12`

pip

pip install --upgrade "salt>=3006.12"

poetry

poetry add "salt>=3006.12"

uv

uv add "salt>=3006.12"

Severity breakdown

CVSS 3.1 8.1

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

Attack vector: Local
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: Low

Weakness

CWE-285: Improper Authorization

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

How to prevent it

Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design: Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Advisories

Packages

Timeline

Jun 13, 2025 Published
Jul 7, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
CVE-2020-16846 SaltStack Salt Command Injection in netapi ssh client	Critical Known exploited	Also affects salt
CVE-2020-11652 SaltStack Salt is vulnerable Arbitrary Directory Access	High Known exploited	Also affects salt
CVE-2020-11651 SaltStack Salt Unauthenticated Remote Code Execution	Critical Known exploited	Also affects salt
GHSA-vcf3-26xf-fw4m Salt Authentication Protocol Version Downgrade Allows Minion Impersonation	Medium	Also affects salt
GHSA-77w2-v593-vxvv Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload	High	Also affects salt
GHSA-8pcp-r83j-fc92 Salt vulnerable to directory traversal attack in file receiving method	High	Also affects salt
GHSA-989c-m532-p2hv Salt's worker process vulnerable to denial of service through file read operation	Medium	Also affects salt
GHSA-7f3f-x5f5-79gw Salt's file contents overwrite the VirtKey class	Medium	Also affects salt

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor