# PraisonAI: Call API localhost-only authentication bypass via spoofed Host header Advisory record · `GHSA-2gpf-2492-q9jh` - **Identifiers:** `GHSA-2gpf-2492-q9jh` · `CVE-2026-61435` · `PYSEC-2026-4247` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html) · [CWE-346](https://cwe.mitre.org/data/definitions/346.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md) - **Published:** 8 Oct 2026 - **Updated:** 15 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 8 Oct 2026, 19:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `praisonai` (PyPI): affected `<4.6.78`; fixed in `4.6.78` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > PraisonAI (PyPI package praisonai) versions before 4.6.78 are affected. When the operator has set PRAISONAI_CALL_AUTH=disabled and the API is reachable over the network, an unauthenticated remote caller can send a spoofed localhost Host header to bypass the intended localhost-only check, then list and invoke registered agents. Upgrade to praisonai 4.6.78 or later. Without the opt-out enabled, the report describes no exposure, and the source gives few details on whether other configurations are affected. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.8 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0049, the 42nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:08 UTC: First seen by agentprime - 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2gpf-2492-q9jh) ## Sources - [GitHub Advisory Database: GHSA-2gpf-2492-q9jh](https://github.com/advisories/GHSA-2gpf-2492-q9jh) - [OSV: GHSA-2gpf-2492-q9jh](https://osv.dev/vulnerability/GHSA-2gpf-2492-q9jh) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .