{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33644 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33644 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33644 is a low-severity server-side request forgery vulnerability in LycheeOrg Lychee, published on 26 Mar 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-33644 and fix it if it is affected.\n\nWhat it is: CVE-2026-33644 is a low-severity server-side request forgery vulnerability in LycheeOrg Lychee, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33644 in the wild and no public exploit code.\n\nAffected product: LycheeOrg Lychee. 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-33644/ (Markdown: https://insights.sbomify.com/CVE-2026-33644/index.md)","id":"CVE-2026-33644","markdown":"https://insights.sbomify.com/CVE-2026-33644/index.md","name":"CVE-2026-33644","record":{"aliases":["GHSA-5245-4p8c-jwff"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lychee photo manager","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in Lychee via DNS rebinding to access internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lychee","vendor":"lycheeorg"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Lychee is a free, open-source photo-management tool. Prior to version 7.5.2, the SSRF protection in `PhotoUrlRule.php` can be bypassed using DNS rebinding. The IP validation check (line 86-89) only activates when the hostname is an IP address. When a domain name is used, `filter_var($host, FILTER_VALIDATE_IP)` returns `false`, skipping the entire check. Version 7.5.2 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in Lychee","id":"CVE-2026-33644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Fireshare has Path Traversal Arbitrary File Write in `/api/uploadChunked`","id":"CVE-2026-33645"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2026-33643"},"products":["Lychee"],"published":"2026-03-26","related":[{"cvss_score":8.8,"headline":"Lychee is vulnerable to an SQL Injection in explain DB queries.","id":"CVE-2023-52082","kev_date_added":null,"published":"2023-12-28"},{"cvss_score":8.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-25808","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-25807","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-43675","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":5.3,"headline":"Lychee has SSRF bypass via incomplete IP validation in Photo::fromUrl — loopback and link-local IPs not blocked","id":"CVE-2026-33537","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":4.8,"headline":"Lychee Vulnerable to Stored XSS via Photo Description in RSS/Atom/JSON Feed (No Sanitization on Public Endpoint)","id":"CVE-2026-33738","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":2.3,"headline":"Missing authorization in Lychee","id":"CVE-2026-39957","kev_date_added":null,"published":"2026-04-09"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["LycheeOrg"]},"summary":"Attackers can bypass SSRF protections in Lychee via DNS rebinding to access internal network resources.","url":"https://insights.sbomify.com/CVE-2026-33644/"}