dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-68971

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In Forgejo through 13.0.3, the attachment component allows a denial of service by uploading a multi-gigabyte file attachment (e.g., to be associated with an issue or a release).

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

In Forgejo through 13.0.3, the attachment upload feature lacks proper file size validation, allowing attackers to upload multi-gigabyte file attachments to issues or releases. This can exhaust storage, memory, or bandwidth resources, causing denial of service for legitimate users.

MitigationImplement and enforce maximum file size limits for attachments at the application or web server level, and add upload validation checks to reject oversized files before processing.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check installed Forgejo version
    Run `forgejo --version` or check the application binary/version file to determine the running version. Compare against the affected range: any version through 13.0.3 is vulnerable.
    Affected if The installed version is 13.0.3 or earlier.
  2. Verify attachment upload is enabled
    Check the Forgejo configuration file (usually app.ini) for the `attachment` section. Look for the `enabled` setting under `[attachment]`. If missing or set to true, uploads are permitted.
    Affected if Attachment uploads are enabled in the configuration.
  3. Inspect attachment size limits
    In the same `[attachment]` section of app.ini, examine the `max_size` setting (values typically in MB). If this setting is absent, set to 0, or set to an excessively large value (e.g., exceeding available storage), no effective limit exists.
    Affected if No `max_size` is defined or it is set to an unlimited/large value.
  4. Confirm upload is allowed on issues and releases
    Review the `[attachment]` configuration for `allow_on_issues` and `allow_on_releases` settings (or equivalent). If these are not explicitly disabled, attachments can be uploaded to these areas.
    Affected if Uploads are permitted to issues or releases.

A user is affected if they run Forgejo version 13.0.3 or earlier with attachment uploads enabled and without enforced size limits.

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

Implement and enforce maximum file size limits for attachments at the application or web server level, and add upload validation checks to reject oversized files before processing.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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