dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-53653

HIGH · 8.7 CVSS v4.0 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

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
Grav is a file-based Web platform. Prior to 1.7.53 and 2.0.0-rc.8, Grav allows an unauthenticated visitor to exhaust server memory and CPU by requesting image derivatives with oversized dimensions through URL query image actions such as forceResize in Grav::fallbackUrl, which passes request parameters to ImageMedium magic actions without a dimension or pixel ceiling. This issue is fixed in versions 1.7.53 and 2.0.0-rc.8.

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

Grav CMS allows unauthenticated visitors to trigger excessive resource consumption by requesting image derivatives with oversized dimensions via URL query parameters (e.g., forceResize). The ImageMedium class in Grav::fallbackUrl passes these parameters without enforcing dimension or pixel ceilings, leading to server memory and CPU exhaustion.

MitigationUpgrade to Grav version 1.7.53 or 2.0.0-rc.8 or later, which implements required dimension and pixel ceilings to prevent resource exhaustion attacks.

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:N/VI:N/VA:H/SC:N/SI:N/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. Identify Grav CMS installation
    Locate the Grav installation by checking for the presence of 'index.php' and 'system/src/Grav' directory in the web root, or look for the 'vendor/twig/twig' directory which is part of Grav's dependencies.
    Affected if Grav CMS is found on the system
  2. Determine installed Grav version
    Check the VERSION file in the Grav root directory, or inspect the 'version' field in composer.json in the system directory, or query the /admin console for the version information.
    Affected if The installed version is lower than 1.7.53 or 2.0.0-rc.8 (e.g., 1.7.x versions before 1.7.53, or 2.0.0-rc versions before rc.8)
  3. Confirm image processing is accessible
    Verify that the image processing endpoint is web-accessible by attempting a basic image request with a query parameter such as '?forceResize=100x100' on any image URL within the media manager or a page containing images.
    Affected if Image URLs with query parameters like forceResize, resize, or crop are processed without requiring authentication
  4. Check if external requests can trigger image generation
    Test by sending an unauthenticated HTTP request to an image path with an oversized dimension parameter (e.g., ?forceResize=50000x50000) and observe if the server attempts to generate the derivative.
    Affected if The server accepts and attempts to process dimension parameters from unauthenticated requests without rejecting or limiting oversized values

The environment is affected if Grav CMS is running a version prior to 1.7.53 or 2.0.0-rc.8 and the image derivative generation feature is accessible to unauthenticated visitors.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Grav version 1.7.53 or 2.0.0-rc.8 or later, which implements required dimension and pixel ceilings to prevent resource exhaustion attacks.

Recommended fix High confidence

Grav 1.7.53 or Grav 2.0.0-rc.8

  1. Verify your current Grav installation version by checking theVERSION file or admin panel
  2. Back up your Grav installation including all content, configuration, and user data
  3. For Grav 1.x users: Upgrade to version 1.7.53 or later
  4. For Grav 2.x users: Upgrade to version 2.0.0-rc.8 or later
  5. After upgrade, verify the ImageMedium class includes dimension limits by checking the commit at d9f9f0369a07ae5c96cde700c7949e1237b29cf6
  6. Test image resize functionality with normal and oversized dimensions to confirm the limit is enforced
  7. Monitor server resource usage after the upgrade to confirm the vulnerability is mitigated
Caveat Review release notes for 1.7.53 and 2.0.0-rc.8 for any breaking changes; major version upgrades (1.x to 2.x) may have plugin/theme compatibility issues

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53653 — 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-53653 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