{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33953 exists.","fix":"No fix has been published for CVE-2026-33953 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33953 is a high-severity server-side request forgery vulnerability in Kovah LinkAce, published on 27 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-33953 and fix it if it is affected.\n\nWhat it is: CVE-2026-33953 is a high-severity server-side request forgery vulnerability in Kovah LinkAce, published on 27 Mar 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-33953 exists.\n\nAffected product: Kovah LinkAce. 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-33953/ (Markdown: https://insights.sbomify.com/CVE-2026-33953/index.md)","id":"CVE-2026-33953","markdown":"https://insights.sbomify.com/CVE-2026-33953/index.md","name":"CVE-2026-33953","record":{"aliases":["GHSA-wp4g-qw9j-wfjg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LinkAce link archive","requires_auth":"low_privilege","summary":"Authenticated users can bypass SSRF protections to access internal services via hostname resolution in LinkAce.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"linkace","vendor":"linkace"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"LinkAce is a self-hosted archive to collect website links. Versions prior to 2.5.3 block direct requests to private IP literals, but still performs server-side requests to internal-only resources when those resources are referenced through an internal hostname. This allows an authenticated user to trigger server-side requests to internal services reachable by the LinkAce server but not directly reachable by an external user. Version 2.5.3 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce","id":"CVE-2026-33953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"LinkAce discloses private notesto unauthorized authenticated users via the web link detail page","id":"CVE-2026-33954"},"packages":[],"prev":{"headline":"FreeRDP: DoS via WINPR_ASSERT in rts_read_auth_verifier_no_checks","id":"CVE-2026-33952"},"products":["LinkAce"],"published":"2026-03-27","related":[{"cvss_score":8.7,"headline":"LinkAce: Stored XSS in Atom Feed via CDATA Escape in List Description","id":"CVE-2026-27458","kev_date_added":null,"published":"2026-02-21"},{"cvss_score":8.7,"headline":"LinkAce: Stored XSS Vulnerability in Link Title Field Through Social Media Sharing Feature","id":"CVE-2025-62722","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.4,"headline":"LinkAce has a Stored One Click XSS vulnerability","id":"CVE-2025-53838","kev_date_added":null,"published":"2025-09-08"},{"cvss_score":7.7,"headline":"LinkAce affected by SSRF via link creation: NoPrivateIpRule not applied to LinkStoreRequest","id":"CVE-2026-30953","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.6,"headline":"File Upload Vulnerability Leading to XSS in LinkAce v1.15.5","id":"CVE-2024-56508","kev_date_added":null,"published":"2024-12-27"},{"cvss_score":7.3,"headline":"LinkAce Vulnerable to Stored XSS on the Audit Page","id":"CVE-2025-59424","kev_date_added":null,"published":"2025-09-18"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["Kovah"]},"summary":"Authenticated users can bypass SSRF protections to access internal services via hostname resolution in LinkAce.","url":"https://insights.sbomify.com/CVE-2026-33953/"}