What is CVE-2026-55535?

CVE-2026-55535 is PraisonAI: Server-Side Request Forgery via DNS rebinding bypass in webhook_url validation. The supplied enrichment data classifies it as Race Condition mapped to CWE-367 CWE-367; CWE-918 Server-Side Request Forgery (SSRF).

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-55535. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-55535 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-55535 using CVSS 6.8, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumRace Conditionpublic exploit

CVE-2026-55535

CVE-2026-55535 — PraisonAI: Server-Side Request Forgery via DNS rebinding bypass in webhook_url validation

PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, the Jobs API validate_webhook_url() path fails open on socket.gaierror and does not bind the validated address to the later request. An attacker webhook_url can later resolve to 127.0.0.1, 169.254.169.254, or another internal address. This issue is fixed in version 4.6.58.

Published Aug 25, 2026Updated Aug 25, 2026Sources: NVD, MervinPraison (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

MervinPraison

2 products listed

CVSS base

6.8

medium

Remediation

The vendor's own words where we have them.

Upgrade PraisonAI to 4.6.58 or later (pip advisory GHSA-hmfx-4v44-9qw9).

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
MervinPraison	PraisonAI	< 4.6.58	Vulnerable
pip	PraisonAI	<= 4.6.48	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Changed

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.8	CVSS 3.1	medium	2.2	4	GitHub (CNA), MervinPraison (CNA), GHSA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

Alter Execution Logic
Unexpected State
Modify Application Data
Modify Files or Directories

Mitigation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.

CWE-918 · Server-Side Request Forgery (SSRF)

Read Application Data
Execute Unauthorized Code or Commands::

Weakness & attack patterns

CWE-367
CWE-918Server-Side Request Forgery (SSRF)

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-29 · Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race ConditionsCAPEC-27 · Leveraging Race Conditions via Symbolic Links

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable PraisonAI.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.8 (AV:N)
Aug 25, 2026 · NVD
Initial · CVE published
Aug 25, 2026 · NVD
Added · GHSA-hmfx-4v44-9qw9 published (medium)
Aug 25, 2026 · GitHub Security Advisory

References

4 on the record

github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1
Exploit, Third Party Advisory, Mitre
github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58
Exploit, Third Party Advisory, Mitre
github.com/MervinPraison/PraisonAI/security/advisories/GHSA-hmfx-4v44-9qw9
Exploit, Third Party Advisory, Mitre
github.com/advisories/GHSA-hmfx-4v44-9qw9
Exploit, Third Party Advisory

Elsewhere on this site

MervinPraisonevery CVE for this vendor
pipevery CVE for this vendor
Race Conditionsame class
CWE-367other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-55535 is PraisonAI: Server-Side Request Forgery via DNS rebinding bypass in webhook_url validation, a medium vulnerability affecting PraisonAI from MervinPraison, pip. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-55535. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.