CVE-2026-44340: Praison Praisonai path traversal (CVSS 7.5)

Description

PraisonAI is a multi-agent teams system. Prior to version 4.6.37, the _safe_extractall helper that all recipe pull, recipe publish, and recipe unpack flows route through validates each archive member's name for absolute paths, .. segments, and resolved-path escape — but does not validate member.linkname, does not reject symlink/hardlink members, and calls tar.extractall(dest_dir) without filter="data". A bundle that contains a symlink with a name inside dest_dir but a linkname pointing outside it, followed by a regular file whose path traverses through the just-created symlink, escapes dest_dir and lets the attacker write arbitrary content to an attacker-chosen location on the victim's filesystem. This issue has been patched in version 4.6.37.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityHigh

AvailabilityNone

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

Affected products

Praison Praisonai< 4.6.37

Remediation

Fixed in

Praison Praisonai≥ 4.6.37

Patch & vendor advisories

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-9q28-ghcr-c4x3

References

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-9q28-ghcr-c4x3ExploitMitigationVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-44340 being actively exploited?

CVE-2026-44340 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.46%.

How severe is CVE-2026-44340?

CVE-2026-44340 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.46% probability of exploitation.

Which products are affected by CVE-2026-44340?

Affected products include Praison Praisonai.

How do I fix CVE-2026-44340?

Upgrade affected software to a fixed version, for example Praison Praisonai 4.6.37 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-44340 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo