{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-91012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91012 is a critical path traversal vulnerability in Apache Karaf, published on 29 Sep 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-91012 and fix it if it is affected.\n\nWhat it is: CVE-2026-91012 is a critical path traversal vulnerability in Apache Karaf, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-91012 in the wild and no public exploit code.\n\nAffected product: Apache Karaf. 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-91012/ (Markdown: https://insights.sbomify.com/CVE-2026-91012/index.md)","id":"CVE-2026-91012","markdown":"https://insights.sbomify.com/CVE-2026-91012/index.md","name":"CVE-2026-91012","record":{"aliases":["GHSA-q6wq-m79c-29mj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Karaf","requires_auth":"none","summary":"A path traversal vulnerability in Apache Karaf allows manager-role users to write arbitrary files, enabling privilege escalation to admin and potential container takeover.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"karaf","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"org.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties),\nwhich backs the \"config\" MBean and the config:* shell commands, derives the file\nit writes a configuration to from caller-supplied input without checking that\nthe result stays inside ${karaf.etc}:\n\n  *  if the submitted property map contains a felix.fileinstall.filename entry, that value is turned directly into a File (getCfgFileFromProperty), so it can point to any absolute path the Karaf process can write to;\n  *  otherwise the configuration PID is concatenated verbatim into the target file name (generateConfigFilename(): new File(karaf.etc, pid + \".cfg\")), so a PID containing \"..\" segments resolves outside ${karaf.etc}. createFactoryConfiguration() has the same issue via the factory PID/alias.\n\nBoth code paths are reachable by any caller holding the \"manager\" role under Karaf's shipped command/JMX ACL (org.apache.karaf.command.acl.conf.cfg: \"update = manager\"). Such a user can therefore write attacker-controlled content to any file the Karaf process can write, including files the same ACL otherwise reserves to \"admin\" (etc/users.properties, etc/*.acl.*.cfg, etc/org.apache.karaf.management.cfg, and similar), allowing a manager-role user to grant themselves the admin role or otherwise take over the container.\n\nConfigMBeanImpl.install() and the config:install shell command already guarded the equivalent risk on their own code path with a finalname.contains(\"..\") string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to ConfigRepositoryImpl.update() / createFactoryConfiguration() at all.","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":"Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation","id":"CVE-2026-91012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)","id":"CVE-2026-91013"},"packages":[],"prev":{"headline":"EWWW Image Optimizer \u003c 8.7.7 - Author+ Stored XSS via Image Class Attribute Backreference Expansion","id":"CVE-2026-91011"},"products":["Apache Karaf"],"published":"2026-09-29","related":[{"cvss_score":9.8,"headline":"Missing authorization in Apache Karaf","id":"CVE-2026-91048","kev_date_added":null,"published":"2026-09-29"},{"cvss_score":9.8,"headline":"Apache Karaf: JDBC JAAS LDAP injection","id":"CVE-2022-40145","kev_date_added":null,"published":"2022-12-21"},{"cvss_score":9.8,"headline":"XML External Entity Reference in Apache Karaf","id":"CVE-2018-11788","kev_date_added":null,"published":"2019-01-07"},{"cvss_score":8.8,"headline":"Apache Karaf: Authorization bypass in JMX MBean lifecycle operations","id":"CVE-2026-92142","kev_date_added":null,"published":"2026-09-29"},{"cvss_score":8.8,"headline":"Apache Karaf: OS Command Injection in Child-Instance Launch (instance:* / InstancesMBean)","id":"CVE-2026-91006","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":8.8,"headline":"Improper Privilege Management in Apache Karaf","id":"CVE-2018-11786","kev_date_added":null,"published":"2018-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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["Apache Software Foundation"]},"summary":"A path traversal vulnerability in Apache Karaf allows manager-role users to write arbitrary files, enabling privilege escalation to admin and potential container takeover.","url":"https://insights.sbomify.com/CVE-2026-91012/"}