dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-49176

HIGH · 7.3 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
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
A flaw was found in the Big Requests extension. The request length is multiplied by 4 before checking against the maximum allowed size, potentially causing an integer overflow and bypassing the size check.

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 confidence

A vulnerability in the Big Requests extension allows integer overflow during request size validation. The code multiplies the request length by 4 before comparing against the maximum allowed size, causing the value to overflow and bypass the size check, potentially allowing oversized or malicious requests to pass through.

MitigationFix the integer overflow by validating the size before multiplication, using larger integer types to hold the multiplied value, or implementing explicit overflow checks before the multiplication operation.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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 checks

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

  1. Confirm Big Requests extension presence
    Locate and identify the Big Requests extension in your environment - check extension directories, loaded modules, or configuration files where extensions are registered
    Affected if The Big Requests extension is installed and loaded in the environment
  2. Determine Big Requests extension version
    Retrieve the version metadata of the Big Requests extension from its manifest, build info, or version resource
    Affected if The installed version matches or falls within the affected version range containing the overflow vulnerability
  3. Locate request size validation code
    Search the Big Requests extension codebase for the request size validation function that performs the multiplication by 4 before size comparison
    Affected if The code performs 'length * 4' calculation before comparing against maximum allowed size
  4. Verify overflow protection absence
    Examine the size validation routine to confirm there is no explicit overflow check before the multiplication operation, and that smaller integer types are used for the calculation
    Affected if No overflow validation exists prior to the multiply-by-4 operation and the result can overflow
  5. Test request size boundary conditions
    If possible, send test requests with sizes near the integer overflow boundary (near max_uint/4) to observe if oversized requests bypass the size limit
    Affected if Requests exceeding the intended size limit successfully pass validation

The environment is affected if the Big Requests extension is enabled and its request size validation code performs multiplication by 4 without proper overflow checking.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the integer overflow by validating the size before multiplication, using larger integer types to hold the multiplied value, or implementing explicit overflow checks before the multiplication operation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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