dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-46683

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.7.0, there is a SSRF and local file read vulnerability via the xsl-style-sheet option. This issue has been patched in version 1.7.0.

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 confidence

Snappy is a PHP library for generating thumbnails, snapshots, and PDFs from URLs or HTML. Prior to version 1.7.0, the xsl-style-sheet option contains a vulnerability allowing both Server-Side Request Forgery (SSRF) and local file read attacks, enabling attackers to make the server request arbitrary URLs or read sensitive local files.

MitigationUpgrade Snappy PHP library to version 1.7.0 or later to remediate the SSRF and local file read vulnerability.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Snappy installation
    Check your project for the presence of the Snappy library. Look for a vendor/knplabs/knp-snappy directory, or search your composer.json for 'knplabs/knp-snappy' or 'snappy' in the require section.
    Affected if The Snappy PHP library is not present in your project.
  2. Determine installed version
    Examine your composer.lock file for the 'knplabs/knp-snappy' package entry and note the installed version number. Alternatively, check the version.php file within the vendor/knplabs/knp-snappy/src directory.
    Affected if The version is lower than 1.7.0 (e.g., 1.6.x, 1.5.x, etc.).
  3. Identify xsl-style-sheet usage
    Search your codebase for calls to Snappy methods that include the 'xsl-style-sheet' option, such as ->setOption('xsl-style-sheet', $value) or configurations passing this option to the Snappy constructor or output method.
    Affected if Your code passes any value (especially user-supplied or external input) to the xsl-style-sheet option.
  4. Assess input source
    Review how the xsl-style-sheet option value is obtained. Determine whether it comes from user input, URL parameters, configuration files with external data, or other untrusted sources.
    Affected if The xsl-style-sheet value can be influenced by user input or external sources (URLs, file paths from requests, etc.).

You are affected if your project uses Snappy PHP library version prior to 1.7.0 AND utilizes the xsl-style-sheet option with values that could be controlled by attackers, enabling them to perform SSRF attacks or read local files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Snappy PHP library to version 1.7.0 or later to remediate the SSRF and local file read vulnerability.

Recommended fix High confidence

1.7.0

  1. Check the current version of knplabs/knp-snappy-bundle or the snappy library in your composer.json
  2. Update the version requirement in composer.json to ^1.7.0 or 1.7.0
  3. Run 'composer update knplabs/knp-snappy-bundle' or 'composer update' to install the fixed version
  4. Verify the installed version is 1.7.0 or later using 'composer show knplabs/knp-snappy-bundle'
  5. Test your application to ensure the Snappy functionality still works correctly after the upgrade
Caveat Review the library's changelog for any deprecations or breaking changes between your current version and 1.7.0

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46683 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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