CVE-2026-5633
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 vulnerability was determined in assafelovic gpt-researcher up to 3.4.3. Affected is an unknown function of the component ws Endpoint. Executing a manipulation of the argument source_urls can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
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 · high confidenceA Server-Side Request Forgery (SSRF) vulnerability exists in gpt-researcher up to v3.4.3 within the WebSocket endpoint component. By manipulating the 'source_urls' argument, an attacker can cause the server to make arbitrary HTTP requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if gpt-researcher is installedCheck for the gpt-researcher package via pip list, package manager, or by locating the application directoryAffected if The package or application is present on the system
-
Determine the installed versionRun 'pip show gpt-researcher' or check the version file in the application directory to obtain the exact version numberAffected if The version is 3.4.3 or any earlier version (the vulnerability affects up to 3.4.3)
-
Verify WebSocket endpoint exposureInspect application routing or server configuration to confirm a WebSocket endpoint exists and is accessibleAffected if A WebSocket endpoint is exposed and reachable from the network
-
Confirm source_urls parameter handlingReview application code or intercept a WebSocket connection request to see if the source_urls parameter is accepted and processedAffected if The source_urls parameter can be supplied via WebSocket connection
-
Test URL validation behaviorSend a WebSocket message with a crafted source_urls value pointing to an internal resource (e.g., http://127.0.0.1:port or http://169.254.169.254) and observe if the server attempts the requestAffected if The server makes HTTP requests to arbitrary URLs supplied by the client without validation
A user is affected if gpt-researcher version 3.4.3 or earlier is installed and the WebSocket endpoint handling source_urls is accessible and makes unsanitized requests to arbitrary URLs.
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 input validation on the source_urls parameter to restrict requests to an approved list of domains or use a safelist approach. Additionally, apply network segmentation and disable unnecessary outbound connections from the server environment to limit SSRF impact.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5633 — 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-5633 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