{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56589 exists.","fix":"No fix has been published for CVE-2025-56589 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56589 is a high-severity server-side request forgery vulnerability in n/a, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56589 and fix it if it is affected.\n\nWhat it is: CVE-2025-56589 is a high-severity server-side request forgery vulnerability in n/a, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56589 exists.\n\nAffected product: n/a. 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-2025-56589/ (Markdown: https://insights.sbomify.com/CVE-2025-56589/index.md)","id":"CVE-2025-56589","markdown":"https://insights.sbomify.com/CVE-2025-56589/index.md","name":"CVE-2025-56589","record":{"aliases":["GHSA-rgvv-mq36-9qv7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"HTML2PDF SDK","requires_auth":"none","summary":"Attackers can exploit SSRF and LFI in the Apryse HTML2PDF SDK to read local files or make arbitrary requests, potentially leading to data disclosure or system takeover.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"html2pdf","vendor":"apryse"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Local File Inclusion (LFI) and a Server-Side Request Forgery (SSRF) vulnerability was found in the InsertFromHtmlString() function of the Apryse HTML2PDF SDK thru 11.6.0. These vulnerabilities could allow an attacker to read local files on the server or make arbitrary HTTP requests to internal or external services. Both vulnerabilities could lead to the disclosure of sensitive data or potential system takeover.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2025-56589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2025-56590"},"packages":[],"prev":{"headline":"Dolibarr vulnerable to RCE via the computed field parameter","id":"CVE-2025-56588"},"products":["n/a"],"published":"2026-01-22","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-56590","kev_date_added":null,"published":"2026-01-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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can exploit SSRF and LFI in the Apryse HTML2PDF SDK to read local files or make arbitrary requests, potentially leading to data disclosure or system takeover.","url":"https://insights.sbomify.com/CVE-2025-56589/"}