dbcve.org
CWE-290Weakness · CWE-290

CVE-2026-58488

MEDIUM · 6.9 CVSS v4.0 Published 2026-07-13
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 5 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
HedgeDoc is an open source, real-time, collaborative, markdown notes application. Versions prior to 1.11.0 allowed attackers to circumvent the rate-limiting of the /login and /register routes by spoofing IP addresses. HedgeDoc instances checked for CloudFlare's cf-connecting-ip header and used that instead of the users real IP address, if the header was present even when the request did not originate from Cloudflare. This made it possible for an attacker to spam login requests or create multiple arbitrary accounts by sending another cf-connecting-ip header every few requests. The issue has been fixed in version 1.11.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

HedgeDoc versions prior to 1.11.0 trusted the CloudFlare cf-connecting-ip header unconditionally, allowing attackers to spoof this header to bypass IP-based rate limiting on /login and /register endpoints. This IP spoofing vulnerability enabled brute-force login attacks and mass account creation.

MitigationUpgrade to HedgeDoc version 1.11.0 or later, which properly validates that requests originate from CloudFlare before trusting the cf-connecting-ip header.

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:L/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. Determine HedgeDoc version
    Check the installed HedgeDoc version using package manager, docker image tag, or the /api/status endpoint if available. Common methods: 'docker images' for container, package.json for npm installs, or check the version banner in the UI/logs.
    Affected if Installed version is prior to 1.11.0 (any 1.x version below 1.11.0)
  2. Verify CloudFlare is in use
    Inspect incoming HTTP requests to HedgeDoc for the 'cf-connecting-ip' header, or check reverse proxy/load balancer configuration to confirm CloudFlare is positioned in front of the HedgeDoc instance.
    Affected if CloudFlare is serving as the reverse proxy and cf-connecting-ip header is present in requests to HedgeDoc
  3. Confirm rate limiting on authentication endpoints
    Review HedgeDoc configuration for rate limiting settings on /login and /register endpoints. Check config files, environment variables, or the runtime configuration to see if IP-based rate limiting is enabled.
    Affected if Rate limiting is enabled on /login or /register endpoints and relies on the cf-connecting-ip header for IP identification

You are affected if you run HedgeDoc versions prior to 1.11.0 with CloudFlare in front and IP-based rate limiting enabled on authentication endpoints.

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 to HedgeDoc version 1.11.0 or later, which properly validates that requests originate from CloudFlare before trusting the cf-connecting-ip header.

Recommended fix High confidence

1.11.0

  1. Backup the current HedgeDoc installation and database before upgrading
  2. Upgrade HedgeDoc to version 1.11.0 using the standard upgrade procedure for your deployment method (e.g., Docker, npm, or source)
  3. Restart the HedgeDoc service to ensure the new version is running
  4. Verify the fix by checking that cf-connecting-ip headers are now properly validated and only accepted from trusted CloudFlare proxies
  5. Test that rate limiting on /login and /register routes is functioning correctly

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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