{"answers":{"affected":"3 open source packages ship an affected version, including wger. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27838 exists.","fix":"No fix has been published for CVE-2026-27838 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27838 is a low-severity vulnerability in wger-project wger, published on 26 Feb 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-27838 and fix it if it is affected.\n\nWhat it is: CVE-2026-27838 is a low-severity vulnerability in wger-project wger, published on 26 Feb 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-27838 exists.\n\nAffected packages and fixed versions:\n- wger (PyPI): affected all versions up to 2.1; no fix listed\n- wger (PyPI): affected all versions up to 2.1; no fix listed\n- wger (PyPI): affected all versions up to 2.1; no fix listed\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-27838/ (Markdown: https://insights.sbomify.com/CVE-2026-27838/index.md)","id":"CVE-2026-27838","markdown":"https://insights.sbomify.com/CVE-2026-27838/index.md","name":"CVE-2026-27838","record":{"aliases":["GHSA-42cr-w2gr-m54q","PYSEC-2026-3418"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"wger fitness manager","requires_auth":"low_privilege","summary":"Attackers can read other users' workout data by exploiting unscoped cache keys in the wger fitness manager API.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wger","vendor":"wger"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"wger is a free, open-source workout and fitness manager. Five routine detail action endpoints check a cache before calling `self.get_object()`. In versions up to and including 2.4, ache keys are scoped only by `pk` — no user ID is included. When a victim has previously accessed their routine via the API, an attacker can retrieve the cached response for the same PK without any ownership check. Commit e964328784e2ee2830a1991d69fadbce86ac9fbf contains a patch for the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"wger: IDOR via user-unscoped cache keys on routine API actions exposes workout data","id":"CVE-2026-27838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup","id":"CVE-2026-27839"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":null,"source":"GHSA-42cr-w2gr-m54q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":"pkg:pypi/wger","source":"GHSA-42cr-w2gr-m54q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":"pkg:pypi/wger","source":"PYSEC-2026-3418"}],"prev":{"headline":"Dottie vulnerable to prototype pollution bypass via non-first path segments in set() and transform()","id":"CVE-2026-27837"},"products":["wger"],"published":"2026-02-26","related":[{"cvss_score":7.8,"headline":"Improper Restriction of Excessive Authentication Attempts in wger-project/wger","id":"CVE-2022-2650","kev_date_added":null,"published":"2022-11-24"},{"cvss_score":7.6,"headline":"wger has Broken Access Control in the Global Gym Configuration Update Endpoint","id":"CVE-2026-40474","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":5.1,"headline":"wger: Stored XSS via Unescaped License Attribution Fields","id":"CVE-2026-40353","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":4.3,"headline":"wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data","id":"CVE-2026-27835","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":4.3,"headline":"wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup","id":"CVE-2026-27839","kev_date_added":null,"published":"2026-02-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-03","vendors":["wger-project"]},"summary":"Attackers can read other users' workout data by exploiting unscoped cache keys in the wger fitness manager API.","url":"https://insights.sbomify.com/CVE-2026-27838/"}