{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22784 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22784 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22784 is a low-severity missing authorization vulnerability in LycheeOrg Lychee, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22784 and fix it if it is affected.\n\nWhat it is: CVE-2026-22784 is a low-severity missing authorization vulnerability in LycheeOrg Lychee, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-22784 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-22784/ (Markdown: https://insights.sbomify.com/CVE-2026-22784/index.md)","id":"CVE-2026-22784","markdown":"https://insights.sbomify.com/CVE-2026-22784/index.md","name":"CVE-2026-22784","record":{"aliases":["GHSA-jj56-2c54-4f25"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lychee photo management","requires_auth":"none","summary":"Attackers can access other users' password-protected albums by unlocking one album with a shared password, bypassing authorization controls.","user_interaction":"required","vuln_class":"missing_authorization"},"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:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Lychee is a free, open-source photo-management tool. Prior to 7.1.0, an authorization vulnerability exists in Lychee's album password unlock functionality that allows users to gain possibly unauthorized access to other users' password-protected albums. When a user unlocks a password-protected public album, the system automatically unlocks ALL other public albums that share the same password, resulting in a complete authorization bypass. This vulnerability is fixed in 7.1.0.","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":"Lychee cross-album password propagation on Album unlocking","id":"CVE-2026-22784","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"orval MCP client is vulnerable to a code injection attack.","id":"CVE-2026-22785"},"packages":[],"prev":{"headline":"Iris Allows Arbitrary File Deletion via Mass Assignment in Datastore File Management","id":"CVE-2026-22783"},"products":["Lychee"],"published":"2026-01-12","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-01-12","vendors":["LycheeOrg"]},"summary":"Attackers can access other users' password-protected albums by unlocking one album with a shared password, bypassing authorization controls.","url":"https://insights.sbomify.com/CVE-2026-22784/"}