How severe is CVE-2026-60085?

CVE-2026-60085 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-60085 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-60085?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-60085 published?

CVE-2026-60085 was published on 2026-07-15.

CVE-2026-60085

CVE-2026-60085 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-273.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (16th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-273
Published: 2026-07-15
Last modified: 2026-07-15

Description

PraisonAI before 4.6.78 contains an unenforced security policy vulnerability in the default Subprocess Sandbox backend where blocked_commands, blocked_paths, blocked_imports, allow_subprocess, and allow_file_write restrictions are completely ignored. Attackers can execute arbitrary subprocess commands, read sensitive files, and perform destructive operations despite explicit security policy configuration.

Frequently asked questions

What is CVE-2026-60085?: PraisonAI before 4.6.78 contains an unenforced security policy vulnerability in the default Subprocess Sandbox backend where blocked_commands, blocked_paths, blocked_imports, allow_subprocess, and allow_file_write restrictions are completely ignored. Attackers can execute arbitrary subprocess commands, read sensitive files, and perform destructive operations despite explicit security policy configuration.
How severe is CVE-2026-60085?: CVE-2026-60085 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-60085 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-60085?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-60085 published?: CVE-2026-60085 was published on 2026-07-15.

References

Other CWE-273 vulnerabilities

CVE-2015-0278 — Critical (CVSS 10.0): libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain…
CVE-2023-34844 — Critical (CVSS 9.8): Play With Docker < 0.0.2 has an insecure CAP_SYS_ADMIN privileged mode causing the docker container to escape.
CVE-2021-36372 — Critical (CVSS 9.8): In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and…
CVE-2020-24361 — Critical (CVSS 9.8): SNMPTT before 1.4.2 allows attackers to execute shell code via EXEC, PREXEC, or unknown_trap_exec.
CVE-2011-3350 — Critical (CVSS 9.8): masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper…
CVE-2011-2921 — Critical (CVSS 9.8): ktsuss versions 1.4 and prior has the uid set to root and does not drop privileges prior to executing user specified…

Browse all CWE-273 vulnerabilities →