CVE-2026-91012 (GCVE-0-2026-91012)
Vulnerability from cvelistv5
Published
2026-09-29 08:34
Modified
2026-10-01 14:10
Severity ?
Summary
org.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties), which backs the "config" MBean and the config:* shell commands, derives the file it writes a configuration to from caller-supplied input without checking that the result stays inside ${karaf.etc}: * 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; * 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. Both 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. ConfigMBeanImpl.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.
Impacted products
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-09-29T09:15:41.656Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/09/28/8"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 9.8,
              "baseSeverity": "CRITICAL",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "HIGH",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2026-91012",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-01T14:10:12.183455Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-22",
                "description": "CWE-22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-01T14:10:47.838Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "org.apache.karaf.config.core.impl",
          "product": "Apache Karaf",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "4.4.12",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "n0mi1k \u003cnomilksec@gmail.com\u003e"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cdiv\u003e\u003cspan\u003eorg.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties)\u003c/span\u003e,\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\u0026nbsp;\u003ccode\u003e${karaf.etc}\u003c/code\u003e:\u003c/div\u003e\u003cdiv\u003e\u003cul\u003e\u003cli\u003eif the submitted property map contains a\u0026nbsp;\u003ccode\u003efelix.fileinstall.filename\u003c/code\u003e\u0026nbsp;entry, that value is turned directly into a\u0026nbsp;\u003ccode\u003eFile\u003c/code\u003e\u0026nbsp;(\u003ccode\u003egetCfgFileFromProperty\u003c/code\u003e), so it can point to any absolute path the Karaf process can write to;\u003c/li\u003e\u003cli\u003eotherwise the configuration PID is concatenated verbatim into the target file name (\u003ccode\u003egenerateConfigFilename(): new File(karaf.etc, pid + \".cfg\")\u003c/code\u003e), so a PID containing \"..\" segments resolves outside\u0026nbsp;\u003ccode\u003e${karaf.etc}\u003c/code\u003e.\u0026nbsp;\u003ccode\u003ecreateFactoryConfiguration()\u003c/code\u003e\u0026nbsp;has the same issue via the factory PID/alias.\u003c/li\u003e\u003c/ul\u003e\u003cdiv\u003eBoth code paths are reachable by any caller holding the \"manager\" role under Karaf\u0027s shipped command/JMX ACL (\u003ccode\u003eorg.apache.karaf.command.acl.conf.cfg:\u003c/code\u003e\u0026nbsp;\"\u003ccode\u003eupdate = manager\u003c/code\u003e\"). 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 \"\u003ccode\u003eadmin\u003c/code\u003e\" (\u003ccode\u003eetc/users.properties\u003c/code\u003e,\u0026nbsp;\u003ccode\u003eetc/*.acl.*.cfg\u003c/code\u003e,\u0026nbsp;\u003ccode\u003eetc/org.apache.karaf.management.cfg\u003c/code\u003e, and similar), allowing a manager-role user to grant themselves the admin role or otherwise take over the container.\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cspan\u003eConfigMBeanImpl.install()\u003c/span\u003e\u0026nbsp;and the\u0026nbsp;\u003ccode\u003econfig:install\u003c/code\u003e\u0026nbsp;shell command already guarded the equivalent risk on their own code path with a\u0026nbsp;\u003ccode\u003efinalname.contains(\"..\")\u003c/code\u003e\u0026nbsp;string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to\u0026nbsp;\u003ccode\u003eConfigRepositoryImpl.update()\u003c/code\u003e\u0026nbsp;/\u0026nbsp;\u003ccode\u003ecreateFactoryConfiguration()\u003c/code\u003e\u0026nbsp;at all.\u003c/div\u003e"
            }
          ],
          "value": "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\u00a0${karaf.etc}:\n\n  *  if the submitted property map contains a\u00a0felix.fileinstall.filename\u00a0entry, that value is turned directly into a\u00a0File\u00a0(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\u00a0${karaf.etc}.\u00a0createFactoryConfiguration()\u00a0has the same issue via the factory PID/alias.\n\n\nBoth code paths are reachable by any caller holding the \"manager\" role under Karaf\u0027s shipped command/JMX ACL (org.apache.karaf.command.acl.conf.cfg:\u00a0\"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,\u00a0etc/*.acl.*.cfg,\u00a0etc/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\n\n\n\n\n\nConfigMBeanImpl.install()\u00a0and the\u00a0config:install\u00a0shell command already guarded the equivalent risk on their own code path with a\u00a0finalname.contains(\"..\")\u00a0string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to\u00a0ConfigRepositoryImpl.update()\u00a0/\u00a0createFactoryConfiguration()\u00a0at all."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "important"
            },
            "type": "Textual description of severity"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-29T08:34:11.409Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/op8trtz1qxkdwj2rjozhd9yt2yd6nhw4"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation",
      "x_generator": {
        "engine": "Vulnogram 1.0.3"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2026-91012",
    "datePublished": "2026-09-29T08:34:11.409Z",
    "dateReserved": "2026-09-14T16:27:00.736Z",
    "dateUpdated": "2026-10-01T14:10:47.838Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"http://www.openwall.com/lists/oss-security/2026/09/28/8\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2026-09-29T09:15:41.656Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 9.8, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-91012\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-01T14:10:12.183455Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-22\", \"description\": \"CWE-22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-01T14:09:32.361Z\"}}], \"cna\": {\"title\": \"Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation\", \"source\": {\"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"reporter\", \"value\": \"n0mi1k \u003cnomilksec@gmail.com\u003e\"}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"important\"}}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Karaf\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"lessThan\": \"4.4.12\", \"versionType\": \"semver\"}], \"packageName\": \"org.apache.karaf.config.core.impl\", \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://lists.apache.org/thread/op8trtz1qxkdwj2rjozhd9yt2yd6nhw4\", \"tags\": [\"vendor-advisory\"]}], \"x_generator\": {\"engine\": \"Vulnogram 1.0.3\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\\u00a0${karaf.etc}:\\n\\n  *  if the submitted property map contains a\\u00a0felix.fileinstall.filename\\u00a0entry, that value is turned directly into a\\u00a0File\\u00a0(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\\u00a0${karaf.etc}.\\u00a0createFactoryConfiguration()\\u00a0has the same issue via the factory PID/alias.\\n\\n\\nBoth code paths are reachable by any caller holding the \\\"manager\\\" role under Karaf\u0027s shipped command/JMX ACL (org.apache.karaf.command.acl.conf.cfg:\\u00a0\\\"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,\\u00a0etc/*.acl.*.cfg,\\u00a0etc/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\\n\\n\\n\\n\\n\\nConfigMBeanImpl.install()\\u00a0and the\\u00a0config:install\\u00a0shell command already guarded the equivalent risk on their own code path with a\\u00a0finalname.contains(\\\"..\\\")\\u00a0string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to\\u00a0ConfigRepositoryImpl.update()\\u00a0/\\u00a0createFactoryConfiguration()\\u00a0at all.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cdiv\u003e\u003cspan\u003eorg.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties)\u003c/span\u003e,\\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\u0026nbsp;\u003ccode\u003e${karaf.etc}\u003c/code\u003e:\u003c/div\u003e\u003cdiv\u003e\u003cul\u003e\u003cli\u003eif the submitted property map contains a\u0026nbsp;\u003ccode\u003efelix.fileinstall.filename\u003c/code\u003e\u0026nbsp;entry, that value is turned directly into a\u0026nbsp;\u003ccode\u003eFile\u003c/code\u003e\u0026nbsp;(\u003ccode\u003egetCfgFileFromProperty\u003c/code\u003e), so it can point to any absolute path the Karaf process can write to;\u003c/li\u003e\u003cli\u003eotherwise the configuration PID is concatenated verbatim into the target file name (\u003ccode\u003egenerateConfigFilename(): new File(karaf.etc, pid + \\\".cfg\\\")\u003c/code\u003e), so a PID containing \\\"..\\\" segments resolves outside\u0026nbsp;\u003ccode\u003e${karaf.etc}\u003c/code\u003e.\u0026nbsp;\u003ccode\u003ecreateFactoryConfiguration()\u003c/code\u003e\u0026nbsp;has the same issue via the factory PID/alias.\u003c/li\u003e\u003c/ul\u003e\u003cdiv\u003eBoth code paths are reachable by any caller holding the \\\"manager\\\" role under Karaf\u0027s shipped command/JMX ACL (\u003ccode\u003eorg.apache.karaf.command.acl.conf.cfg:\u003c/code\u003e\u0026nbsp;\\\"\u003ccode\u003eupdate = manager\u003c/code\u003e\\\"). 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 \\\"\u003ccode\u003eadmin\u003c/code\u003e\\\" (\u003ccode\u003eetc/users.properties\u003c/code\u003e,\u0026nbsp;\u003ccode\u003eetc/*.acl.*.cfg\u003c/code\u003e,\u0026nbsp;\u003ccode\u003eetc/org.apache.karaf.management.cfg\u003c/code\u003e, and similar), allowing a manager-role user to grant themselves the admin role or otherwise take over the container.\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cspan\u003eConfigMBeanImpl.install()\u003c/span\u003e\u0026nbsp;and the\u0026nbsp;\u003ccode\u003econfig:install\u003c/code\u003e\u0026nbsp;shell command already guarded the equivalent risk on their own code path with a\u0026nbsp;\u003ccode\u003efinalname.contains(\\\"..\\\")\u003c/code\u003e\u0026nbsp;string check, but that check does not stop absolute paths or symlink-based escapes, and it was never applied to\u0026nbsp;\u003ccode\u003eConfigRepositoryImpl.update()\u003c/code\u003e\u0026nbsp;/\u0026nbsp;\u003ccode\u003ecreateFactoryConfiguration()\u003c/code\u003e\u0026nbsp;at all.\u003c/div\u003e\", \"base64\": false}]}], \"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2026-09-29T08:34:11.409Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-91012\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-01T14:10:47.838Z\", \"dateReserved\": \"2026-09-14T16:27:00.736Z\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"datePublished\": \"2026-09-29T08:34:11.409Z\", \"assignerShortName\": \"apache\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…