{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-58488", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-06-30T20:21:25.812Z", "datePublished": "2026-07-13T21:43:14.830Z", "dateUpdated": "2026-07-13T21:43:14.830Z"}, "containers": {"cna": {"title": "HedgeDoc: Rate-limit bypass via CF-Connecting-IP header spoofing", "problemTypes": [{"descriptions": [{"cweId": "CWE-290", "lang": "en", "description": "CWE-290: Authentication Bypass by Spoofing", "type": "CWE"}]}, {"descriptions": [{"cweId": "CWE-770", "lang": "en", "description": "CWE-770: Allocation of Resources Without Limits or Throttling", "type": "CWE"}]}], "metrics": [{"cvssV4_0": {"attackVector": "NETWORK", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "userInteraction": "NONE", "vulnConfidentialityImpact": "NONE", "vulnIntegrityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "baseScore": 6.9, "baseSeverity": "MEDIUM", "vectorString": "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", "version": "4.0"}}], "references": [{"name": "https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-2f9f-w8xq-276v", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-2f9f-w8xq-276v"}], "affected": [{"vendor": "hedgedoc", "product": "hedgedoc", "versions": [{"version": "< 1.11.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-07-13T21:43:14.830Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-2f9f-w8xq-276v", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,1.11.0)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "hedgedoc", "source": "cna", "vendor": "hedgedoc"}, "product": "hedgedoc", "vendor": "hedgedoc"}], "created": "2026-07-14T00:30:01.725458+00:00", "updated": "2026-07-14T00:30:01.725487+00:00", "vendors": ["hedgedoc", "hedgedoc$PRODUCT$hedgedoc"]}