CVE-2026-33659: EspoCRM: SSRF via DNS Rebinding in Attachment fromImageUrl Endpoint Allows Internal Network Access
EspoCRM is an open source customer relationship management application. In versions 9.3.3 and below, the POST /api/v1/Attachment/fromImageUrl endpoint is vulnerable to Server-Side Request Forgery (SSRF) via a DNS rebinding (TOCTOU) condition. Host validation uses dnsgetrecord() but the actual HTTP request resolves hostnames through curl's internal resolver (gethostbyname()), allowing the two lookups to return different IP addresses for the same hostname. A secondary issue exists where an empty DNS result (due to DNS failure, IPv6-only domains, or non-existent hostnames) causes the validation to implicitly allow the host without further checks. An authenticated attacker with default attachment creation access can exploit this gap to bypass internal IP restrictions and scan internal network ports, confirm the existence of internal hosts, and interact with internal HTTP-based services, though data extraction from binary protocol services and remote code execution are not possible through this endpoint. This issue has been fixed in version 9.3.4.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33659?
The severity of CVE-2026-33659 is classified as high due to the potential for internal network access via SSRF.
How do I fix CVE-2026-33659?
To fix CVE-2026-33659, upgrade EspoCRM to version 9.3.4 or later.
Which versions of EspoCRM are affected by CVE-2026-33659?
EspoCRM versions 9.3.3 and below are affected by CVE-2026-33659.
What type of vulnerability is CVE-2026-33659?
CVE-2026-33659 is a Server-Side Request Forgery (SSRF) vulnerability.
What is the impact of CVE-2026-33659 on EspoCRM users?
The impact of CVE-2026-33659 on EspoCRM users includes potential exposure to internal network vulnerabilities and unauthorized access.