CVE-2026-4308
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weakness has been identified in frdel/agent0ai agent-zero 0.9.7. This affects the function handle_pdf_document of the file python/helpers/document_query.py. This manipulation causes server-side request forgery. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceServer-Side Request Forgery (SSRF) vulnerability in the handle_pdf_document function of document_query.py in agent-zero 0.9.7. The function likely accepts user-controlled URLs without proper validation, allowing attackers to make the server request arbitrary internal or external resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed agent-zero versionRun `pip show agent-zero` or check package.json/requirements.txt to find the installed version of agent-zeroAffected if The installed version is 0.9.7 exactly or falls within a range that includes 0.9.7 (e.g., any version from 0.9.0 up to but not including a patched version)
-
Locate document_query.py and verify handle_pdf_document existsFind the document_query.py file in the agent-zero installation (typically in the source directory) and confirm the handle_pdf_document function is presentAffected if The file and function exist in the installed version matching 0.9.7
-
Inspect handle_pdf_document for URL validationOpen document_query.py and examine the handle_pdf_document function code. Look for URL validation, allowlists, or input sanitization on any URL parameterAffected if The function accepts URL parameters without proper validation (no allowlist, no domain restrictions, no protocol checks)
-
Determine if function is exposed via API or web interfaceCheck if handle_pdf_document is bound to an API route, web endpoint, or other user-accessible interface. Review routing configuration or entry pointsAffected if The function is exposed as a callable endpoint accessible to users or external inputs
You are affected if you are running agent-zero version 0.9.7 and the handle_pdf_document function is accessible (e.g., via API) without URL validation controls in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based URL validation and restrict the handle_pdf_document function to only accept URLs from trusted domains or protocols. Consider disabling outbound requests entirely if PDFs are uploaded directly.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4308 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data