{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33534 exists.","fix":"No fix has been published for CVE-2026-33534 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33534 is a medium-severity server-side request forgery vulnerability in espocrm, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33534 and fix it if it is affected.\n\nWhat it is: CVE-2026-33534 is a medium-severity server-side request forgery vulnerability in espocrm, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33534 exists.\n\nAffected product: espocrm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33534/ (Markdown: https://insights.sbomify.com/CVE-2026-33534/index.md)","id":"CVE-2026-33534","markdown":"https://insights.sbomify.com/CVE-2026-33534/index.md","name":"CVE-2026-33534","record":{"aliases":["GHSA-h7gx-8gwv-7g73"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EspoCRM application","requires_auth":"low_privilege","summary":"Authenticated attackers can bypass internal host validation using alternative IPv4 notations to access loopback services and read internal data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"espocrm","vendor":"espocrm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"EspoCRM is an open source customer relationship management application. Versions 9.3.3 and below have an authenticated Server-Side Request Forgery (SSRF) vulnerability that allows bypassing the internal-host validation logic by using alternative IPv4 representations such as octal notation (e.g., 0177.0.0.1 instead of 127.0.0.1). This is caused by HostCheck::isNotInternalHost() function relying on PHP's filter_var(..., FILTER_VALIDATE_IP), which does not recognize alternative IP formats, causing the validation to fall through to a DNS lookup that returns no records and incorrectly treats the host as safe, however the cURL subsequently normalizes the address and connects to the loopback destination. Through the confirmed /api/v1/Attachment/fromImageUrl endpoint, an authenticated user can force the server to make requests to loopback-only services and store the fetched response as an attachment. This vulnerability is distinct from CVE-2023-46736 (which involved redirect-based SSRF) and may allow access to internal resources reachable from the application runtime. This issue has been fixed in version 9.3.4.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-05-08","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-05-08T17:22:43Z","kind":"github_poc","ref":"https://github.com/EntroVyx/CVE-2026-33534","stars":0,"title":"EspoCRM 9.3.3 - Authenticated SSRF via Alternative IPv4 Notation"},{"date":"2026-05-27","kind":"exploitdb","ref":"52583","stars":null,"title":"EspoCRM 9.3.3 -  SSRF"},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-33534.yaml","stars":null,"title":"EspoCRM \u003c= 9.3.3 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":false,"headline":"EspoCRM has authenticated SSRF via internal-host validation bypass using alternative IPv4 notation","id":"CVE-2026-33534","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ImageMagick has an Out-of-Bounds write of a zero byte in its X11 display interaction","id":"CVE-2026-33535"},"packages":[],"prev":{"headline":"Glances Vulnerable to Cross-Origin System Information Disclosure via XML-RPC Server CORS Wildcard","id":"CVE-2026-33533"},"products":["espocrm"],"published":"2026-04-13","related":[{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2014-7985","kev_date_added":null,"published":"2014-10-31"},{"cvss_score":9.1,"headline":"Path traversal in espocrm","id":"CVE-2026-33656","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-38843","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-14351","kev_date_added":null,"published":"2019-07-28"},{"cvss_score":8.6,"headline":"EspoCRM 5.7.0 \u003c 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords","id":"CVE-2020-37094","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8,"headline":"Code injection in n/a","id":"CVE-2022-38844","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.2,"headline":"EspoCRM has Admin TemplateManager path traversal that allows arbitrary file read write and delete","id":"CVE-2026-33733","kev_date_added":null,"published":"2026-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-14","vendors":["espocrm"]},"summary":"Authenticated attackers can bypass internal host validation using alternative IPv4 notations to access loopback services and read internal data.","url":"https://insights.sbomify.com/CVE-2026-33534/"}