ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-6pjq-v35w-jmjh

Unauthenticated long body request loads CPU in the password-redaction regex, denying service

Published Oct 13, 2026 · catalog updated Oct 13, 2026 · Unauthenticated long body request

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-6pjq-v35w-jmjh. A missing EPSS score is not a low risk. Compare Unauthenticated long body request with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Unauthenticated long body request).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
See sources for product scope

## Summary An unauthenticated attacker can send specially crafted API requests that trigger excessive CPU usage during error handling. By sending a small number of large requests concurrently, an attacker can exhaust available server workers, making EspoCRM slow or unavailable to legitimate users.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix GHSA-6pjq-v35w-jmjh

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-6pjq-v35w-jmjh. A missing EPSS score is not a low risk. Compare Unauthenticated long body request with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

EspoCRM security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · Maintainer security tabs

    Detected

    ## Summary An unauthenticated attacker can send specially crafted API requests that trigger excessive CPU usage during error handling. By sending a small number of large requests concurrently, an attacker can exhaust available server workers, making EspoCRM slow or unavailable to legitimate users.

Sources

  • Maintainer security tabsVendor advisoryGHSA-6pjq-v35w-jmjh

    ## Summary An unauthenticated attacker can send specially crafted API requests that trigger excessive CPU usage during error handling. By sending a small number of large requests concurrently, an attacker can exhaust available server workers, making EspoCRM slow or unavailable to legitimate users.

    github.com

Freshness

Last verified in this catalog Oct 13, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026