CVE-2026-5936
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 · uneditedAn attacker can control a server-side HTTP request by supplying a crafted URL, causing the server to initiate requests to arbitrary destinations. This behavior may be exploited to probe internal network services, access otherwise unreachable endpoints (e.g., cloud metadata services), or bypass network access controls, potentially leading to sensitive information disclosure and further compromise of the internal environment.
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 where an attacker can control server-side HTTP requests by supplying a crafted URL. This allows the server to initiate requests to arbitrary destinations, enabling internal network probing, access to cloud metadata services (e.g., AWS169.254.169.254), and bypass of network access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026-04-07CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Foxit Pdf Services Api installationLocate and determine the installed version of Foxit Pdf Services Api in your environment. Check product documentation, installed software inventory, or API service metadata for version information.Affected if The installed version is earlier than the 2026-04-07 release date.
-
Confirm API accepts external URL inputReview application configurations, API endpoints, and input handling code to determine if the service accepts user-supplied or externally sourced URLs as parameters.Affected if The service processes or makes HTTP requests based on user-provided URLs.
-
Audit outbound HTTP request loggingExamine network logs, proxy logs, or application logs for outbound HTTP/HTTPS requests initiated by the Foxit Pdf Services Api process.Affected if There are outbound requests to unexpected or arbitrary destinations, particularly internal network addresses or cloud metadata endpoints (e.g., 169.254.169.254).
You are affected if Foxit Pdf Services Api version is before 2026-04-07 AND the service accepts or processes URLs from untrusted sources.
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.
dbcve · scoped2026-04-07
Implement strict URL allow-listing and input validation for user-supplied URLs, restrict outbound HTTP requests to trusted domains/IPs, disable unnecessary outgoing network connections, and apply network segmentation to isolate sensitive internal services from web-facing components.
Pdf Services Api version 2026-04-07 or later
- 1. Identify all deployments of Foxit PDF Services API currently in use
- 2. Check the current version of the Pdf Services Api installation
- 3. If the version is earlier than 2026-04-07, plan for upgrade to version 2026-04-07 or later
- 4. Before upgrading, review release notes for any breaking changes or migration requirements
- 5. Perform the upgrade in a test/staging environment first
- 6. Validate that the upgrade completes successfully and all functionality works as expected
- 7. Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5936 — 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-5936 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