{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33954 exists.","fix":"No fix has been published for CVE-2026-33954 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33954 is a medium-severity missing authorization 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-33954 and fix it if it is affected.\n\nWhat it is: CVE-2026-33954 is a medium-severity missing authorization 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-33954 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-33954/ (Markdown: https://insights.sbomify.com/CVE-2026-33954/index.md)","id":"CVE-2026-33954","markdown":"https://insights.sbomify.com/CVE-2026-33954/index.md","name":"CVE-2026-33954","record":{"aliases":["GHSA-88h3-cq25-vw8q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LinkAce link archive","requires_auth":"low_privilege","summary":"Authenticated users can view private notes on shared links due to missing visibility checks on the web interface.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"linkace","vendor":"linkace"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"LinkAce is a self-hosted archive to collect website links. In versions prior to 2.5.3, a private note attached to a non-private link can be disclosed to a different authenticated user via the web interface. The API appears to correctly enforce note visibility, but the web link detail page renders notes without applying equivalent visibility filtering. As a result, an authenticated user who is allowed to view another user's `internal` or `public` link can read that user's `private` notes attached to the link. 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 discloses private notesto unauthorized authenticated users via the web link detail page","id":"CVE-2026-33954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Notesnook vulnerable to RCE via stored XSS in Note History diff viewer","id":"CVE-2026-33955"},"packages":[],"prev":{"headline":"LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce","id":"CVE-2026-33953"},"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.5,"headline":"LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce","id":"CVE-2026-33953","kev_date_added":null,"published":"2026-03-27"},{"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-27","vendors":["Kovah"]},"summary":"Authenticated users can view private notes on shared links due to missing visibility checks on the web interface.","url":"https://insights.sbomify.com/CVE-2026-33954/"}