{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104108 exists.","fix":"No fix has been published for CVE-2026-104108 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104108 is a high-severity authentication bypass vulnerability in error311 FileRise, published on 14 Oct 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-2026-104108 and fix it if it is affected.\n\nWhat it is: CVE-2026-104108 is a high-severity authentication bypass vulnerability in error311 FileRise, published on 14 Oct 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-2026-104108 exists.\n\nAffected product: error311 FileRise. 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-104108/ (Markdown: https://insights.sbomify.com/CVE-2026-104108/index.md)","id":"CVE-2026-104108","markdown":"https://insights.sbomify.com/CVE-2026-104108/index.md","name":"CVE-2026-104108","record":{"aliases":["GHSA-c5c5-mv9m-j367"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"FileRise file manager","requires_auth":"none","summary":"Attackers can hijack local accounts, including admin, by exploiting mutable OIDC claims in FileRise, requiring a vulnerable identity provider configuration.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise maps an authenticated OIDC identity to a local account using mutable preferred_username or email claims and does not require email_verified for email-based naming. An attacker who can obtain provider-issued claims colliding with an existing local username can be logged in as that account, including the built-in administrator, even when automatic provisioning is disabled. Exploitability depends on the configured identity provider allowing the colliding claim. This issue is fixed in version 3.23.0.","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":"FileRise OIDC login can bind an attacker identity to an existing local account","id":"CVE-2026-104108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FileRise: Authenticated ZIP extraction follows a pre-existing symlink and deletes files outside the storage root","id":"CVE-2026-104109"},"packages":[],"prev":{"headline":"FileRise: Authenticated path traversal escapes configured storage root through inherited ACLs","id":"CVE-2026-104107"},"products":["FileRise"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["error311"]},"summary":"Attackers can hijack local accounts, including admin, by exploiting mutable OIDC claims in FileRise, requiring a vulnerable identity provider configuration.","url":"https://insights.sbomify.com/CVE-2026-104108/"}