Vulnerability-Lookup

CVE-2026-39306 (GCVE-0-2026-39306)

Vulnerability from cvelistv5 – Published: 2026-04-07 16:48 – Updated: 2026-04-07 18:31

Title

PraisonAI recipe registry pull path traversal writes files outside the chosen output directory

Summary

PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI's recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113.

Severity ?

7.3 (High)


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

CWE

CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Assigner

GitHub_M

References

URL

Tags

https://github.com/MervinPraison/PraisonAI/securi…

x_refsource_CONFIRM

Impacted products

	Vendor	Product	Version
	MervinPraison	PraisonAI	Affected: < 4.5.113

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-39306",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-04-07T18:31:17.535173Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-04-07T18:31:31.939Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "PraisonAI",
          "vendor": "MervinPraison",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 4.5.113"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI\u0027s recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-22",
              "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-07T16:48:05.722Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534"
        }
      ],
      "source": {
        "advisory": "GHSA-4rx4-4r3x-6534",
        "discovery": "UNKNOWN"
      },
      "title": "PraisonAI recipe registry pull path traversal writes files outside the chosen output directory"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-39306",
    "datePublished": "2026-04-07T16:48:05.722Z",
    "dateReserved": "2026-04-06T19:31:07.265Z",
    "dateUpdated": "2026-04-07T18:31:31.939Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-39306\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-04-07T17:16:36.470\",\"lastModified\":\"2026-04-08T21:27:00.663\",\"vulnStatus\":\"Undergoing Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI\u0027s recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H\",\"baseScore\":7.3,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"REQUIRED\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.1,\"impactScore\":5.2}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-22\"}]}],\"references\":[{\"url\":\"https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534\",\"source\":\"security-advisories@github.com\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-39306\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-04-07T18:31:17.535173Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-04-07T18:31:27.583Z\"}}], \"cna\": {\"title\": \"PraisonAI recipe registry pull path traversal writes files outside the chosen output directory\", \"source\": {\"advisory\": \"GHSA-4rx4-4r3x-6534\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.3, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"REQUIRED\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}], \"affected\": [{\"vendor\": \"MervinPraison\", \"product\": \"PraisonAI\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 4.5.113\"}]}], \"references\": [{\"url\": \"https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534\", \"name\": \"https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534\", \"tags\": [\"x_refsource_CONFIRM\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI\u0027s recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-22\", \"description\": \"CWE-22: Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-04-07T16:48:05.722Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-39306\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-04-07T18:31:31.939Z\", \"dateReserved\": \"2026-04-06T19:31:07.265Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-04-07T16:48:05.722Z\", \"assignerShortName\": \"GitHub_M\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

GHSA-4RX4-4R3X-6534

Vulnerability from github – Published: 2026-04-06 23:09 – Updated: 2026-04-07 22:10

Summary

PraisonAI recipe registry pull path traversal writes files outside the chosen output directory

Details

Summary

PraisonAI's recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected.

This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself.

Details

The issue is caused by unsafe extraction of tar archive contents during recipe pull.

A malicious publisher creates a valid .praison bundle whose manifest.json is benign enough to pass publish, but whose tar members include traversal entries such as:

../../escape-http.txt

LocalRegistry.publish() in src/praisonai/praisonai/recipe/registry.py:214-287 only reads manifest.json, calculates a checksum, and stores the uploaded bundle. It does not inspect or sanitize the rest of the tar members before saving the archive.
When a victim later pulls the recipe from a local registry, LocalRegistry.pull() in src/praisonai/praisonai/recipe/registry.py:289-345 extracts the tarball directly:

recipe_dir = output_dir / name
recipe_dir.mkdir(parents=True, exist_ok=True)

with tarfile.open(bundle_path, "r:gz") as tar:
    tar.extractall(recipe_dir)

The HTTP client path is also vulnerable. HttpRegistry.pull() in src/praisonai/praisonai/recipe/registry.py:691-739 downloads the bundle and then performs the same unsafe extraction:

recipe_dir = output_dir / name
recipe_dir.mkdir(parents=True, exist_ok=True)

with tarfile.open(bundle_path, "r:gz") as tar:
    tar.extractall(recipe_dir)

Because no archive member validation is performed, traversal entries escape recipe_dir and create files elsewhere on disk.

Verified vulnerable behavior:

Published recipe name: evil-http
Victim-selected output directory: /tmp/praisonai-pull-traversal-poc/victim-output
Artifact created outside that directory: /tmp/praisonai-pull-traversal-poc/escape-http.txt
Artifact contents: owned over http

This demonstrates that a remote publisher can cause filesystem writes outside the pull destination chosen by another user.

PoC

Run the single verification script from the checked-out repository:

cd "/Users/r1zzg0d/Documents/CVE hunting/targets/PraisonAI"
python3 tmp/pocs/poc2.py

Expected vulnerable output:

[+] Publish result: {'ok': True, 'name': 'evil-http', 'version': '1.0.0', ...}
[+] Pull result: {'name': 'evil-http', 'version': '1.0.0', ...}
[+] Outside artifact exists: True
[+] Artifact also inside output dir: False
[+] Outside artifact content: 'owned over http\n'
[+] RESULT: VULNERABLE - pulling the recipe created a file outside the chosen output directory.

Then verify the created file manually:

ls -l /tmp/praisonai-pull-traversal-poc/escape-http.txt
cat /tmp/praisonai-pull-traversal-poc/escape-http.txt
find /tmp/praisonai-pull-traversal-poc -maxdepth 3 | sort

What the script does internally:

Starts a local PraisonAI recipe registry server.
Builds a malicious .praison bundle containing the tar entry ../../escape-http.txt.
Publishes the malicious bundle to the local HTTP registry.
Simulates a victim pulling that recipe into /tmp/praisonai-pull-traversal-poc/victim-output.
Confirms that the file is created outside the chosen output directory.

Impact

This is a path traversal / arbitrary file write vulnerability in the recipe pull workflow.

Impacted parties:

Users who pull recipes from an untrusted or shared PraisonAI registry.
Teams running internal registries where one publisher can influence what other users pull.
Automated systems or CI jobs that fetch recipes into working directories near sensitive project files.

Security impact:

Integrity impact is high because an attacker can create or overwrite files outside the expected extraction directory.
Availability impact is significant if the overwritten target is a config file, project file, startup script, or another operational artifact.
The issue crosses a real security boundary because the attacker only needs to publish a malicious recipe, while the victim triggers the write by pulling it.

Remediation

Replace raw tar.extractall() with a safe extraction routine that validates every TarInfo member before extraction. Reject absolute paths, .. segments, and any resolved path that escapes the intended extraction directory.
Apply the same archive member validation in both LocalRegistry.pull() and HttpRegistry.pull() so that local and remote registry clients share the same safety guarantees.
Consider validating tar contents during publish as well, so malicious bundles are rejected before they ever enter the registry and cannot be served to downstream users.

Severity ?

7.3 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 4.5.112"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "PraisonAI"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.5.113"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-39306"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-06T23:09:12Z",
    "nvd_published_at": "2026-04-07T17:16:36Z",
    "severity": "HIGH"
  },
  "details": "### Summary\n\nPraisonAI\u0027s recipe registry pull flow extracts attacker-controlled `.praison` tar archives with `tar.extractall()` and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains `../` traversal entries and any user who later pulls that recipe will write files outside the output directory they selected.\n\nThis is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself.\n\n### Details\n\nThe issue is caused by unsafe extraction of tar archive contents during recipe pull.\n\n1. A malicious publisher creates a valid `.praison` bundle whose `manifest.json` is benign enough to pass publish, but whose tar members include traversal entries such as:\n\n```text\n../../escape-http.txt\n```\n\n2. `LocalRegistry.publish()` in `src/praisonai/praisonai/recipe/registry.py:214-287` only reads `manifest.json`, calculates a checksum, and stores the uploaded bundle. It does not inspect or sanitize the rest of the tar members before saving the archive.\n\n3. When a victim later pulls the recipe from a local registry, `LocalRegistry.pull()` in `src/praisonai/praisonai/recipe/registry.py:289-345` extracts the tarball directly:\n\n```python\nrecipe_dir = output_dir / name\nrecipe_dir.mkdir(parents=True, exist_ok=True)\n\nwith tarfile.open(bundle_path, \"r:gz\") as tar:\n    tar.extractall(recipe_dir)\n```\n\n4. The HTTP client path is also vulnerable. `HttpRegistry.pull()` in `src/praisonai/praisonai/recipe/registry.py:691-739` downloads the bundle and then performs the same unsafe extraction:\n\n```python\nrecipe_dir = output_dir / name\nrecipe_dir.mkdir(parents=True, exist_ok=True)\n\nwith tarfile.open(bundle_path, \"r:gz\") as tar:\n    tar.extractall(recipe_dir)\n```\n\n5. Because no archive member validation is performed, traversal entries escape `recipe_dir` and create files elsewhere on disk.\n\nVerified vulnerable behavior:\n\n- Published recipe name: `evil-http`\n- Victim-selected output directory: `/tmp/praisonai-pull-traversal-poc/victim-output`\n- Artifact created outside that directory: `/tmp/praisonai-pull-traversal-poc/escape-http.txt`\n- Artifact contents: `owned over http`\n\nThis demonstrates that a remote publisher can cause filesystem writes outside the pull destination chosen by another user.\n\n### PoC\n\nRun the single verification script from the checked-out repository:\n\n```bash\ncd \"/Users/r1zzg0d/Documents/CVE hunting/targets/PraisonAI\"\npython3 tmp/pocs/poc2.py\n```\n\nExpected vulnerable output:\n\n```text\n[+] Publish result: {\u0027ok\u0027: True, \u0027name\u0027: \u0027evil-http\u0027, \u0027version\u0027: \u00271.0.0\u0027, ...}\n[+] Pull result: {\u0027name\u0027: \u0027evil-http\u0027, \u0027version\u0027: \u00271.0.0\u0027, ...}\n[+] Outside artifact exists: True\n[+] Artifact also inside output dir: False\n[+] Outside artifact content: \u0027owned over http\\n\u0027\n[+] RESULT: VULNERABLE - pulling the recipe created a file outside the chosen output directory.\n```\n\nThen verify the created file manually:\n\n```bash\nls -l /tmp/praisonai-pull-traversal-poc/escape-http.txt\ncat /tmp/praisonai-pull-traversal-poc/escape-http.txt\nfind /tmp/praisonai-pull-traversal-poc -maxdepth 3 | sort\n```\n\nWhat the script does internally:\n\n1. Starts a local PraisonAI recipe registry server.\n2. Builds a malicious `.praison` bundle containing the tar entry `../../escape-http.txt`.\n3. Publishes the malicious bundle to the local HTTP registry.\n4. Simulates a victim pulling that recipe into `/tmp/praisonai-pull-traversal-poc/victim-output`.\n5. Confirms that the file is created outside the chosen output directory.\n\n### Impact\n\nThis is a path traversal / arbitrary file write vulnerability in the recipe pull workflow.\n\nImpacted parties:\n\n- Users who pull recipes from an untrusted or shared PraisonAI registry.\n- Teams running internal registries where one publisher can influence what other users pull.\n- Automated systems or CI jobs that fetch recipes into working directories near sensitive project files.\n\nSecurity impact:\n\n- Integrity impact is high because an attacker can create or overwrite files outside the expected extraction directory.\n- Availability impact is significant if the overwritten target is a config file, project file, startup script, or another operational artifact.\n- The issue crosses a real security boundary because the attacker only needs to publish a malicious recipe, while the victim triggers the write by pulling it.\n\n### Remediation\n\n1. Replace raw `tar.extractall()` with a safe extraction routine that validates every `TarInfo` member before extraction. Reject absolute paths, `..` segments, and any resolved path that escapes the intended extraction directory.\n\n2. Apply the same archive member validation in both `LocalRegistry.pull()` and `HttpRegistry.pull()` so that local and remote registry clients share the same safety guarantees.\n\n3. Consider validating tar contents during publish as well, so malicious bundles are rejected before they ever enter the registry and cannot be served to downstream users.",
  "id": "GHSA-4rx4-4r3x-6534",
  "modified": "2026-04-07T22:10:07Z",
  "published": "2026-04-06T23:09:12Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-39306"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/MervinPraison/PraisonAI"
    },
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/releases/tag/v4.5.113"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "PraisonAI recipe registry pull path traversal writes files outside the chosen output directory"
}

FKIE_CVE-2026-39306

Vulnerability from fkie_nvd - Published: 2026-04-07 17:16 - Updated: 2026-04-08 21:27

Severity ?

7.3 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H

Summary

References

	URL	Tags
	security-advisories@github.com	https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI\u0027s recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113."
    }
  ],
  "id": "CVE-2026-39306",
  "lastModified": "2026-04-08T21:27:00.663",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.3,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.1,
        "impactScore": 5.2,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-04-07T17:16:36.470",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2026-39306 (GCVE-0-2026-39306)

GHSA-4RX4-4R3X-6534

Summary

Details

PoC

Impact

Remediation

FKIE_CVE-2026-39306

Tags

Sightings

Nomenclature