GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2026-82437 (GCVE-0-2026-82437)

Vulnerability from cvelistv5 – Published: 2026-09-14 14:05 – Updated: 2026-09-14 19:54
VLAI
Title
Apache Storm Logviewer: Log Access Controls Not Enforced by Logviewer
Summary
Description The Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For daemon logs those settings were not applied: the access decision combined the "this is a daemon log" flag with the authorizer result in a way that discarded the authorizer's answer whenever the flag was set, and the daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any user able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the other daemon logs on every reachable node, which contain other tenants' topology names, owners and configuration fragments. The same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so `/listLogs` and `/searchLogs` returned every tenant's topology and worker log file names regardless of the caller. That part is metadata only. There was no configuration that closed either behaviour. Mitigation Upgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the worker log paths already used, and the listing endpoints filter by the requesting user. Users who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the daemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-09-14 19:54 UTC
CWE
Impacted products
Vendor Product Version CPE status
Apache Software Foundation Apache Storm Logviewer Affected: 3.0.0 , < 3.1.0 (semver)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-09-14T14:13:39.910Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/09/13/16"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 4.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "LOW",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2026-82437",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-14T19:54:14.405653Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-14T19:54:36.871Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "org.apache.storm:storm-webapp",
          "product": "Apache Storm Logviewer",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "3.1.0",
              "status": "affected",
              "version": "3.0.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "The ASF using Claude Agents"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cb\u003eDescription\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eThe Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For\u003cbr\u003edaemon logs those settings were not applied: the access decision combined the \"this is a daemon log\" flag\u003cbr\u003ewith the authorizer result in a way that discarded the authorizer\u0027s answer whenever the flag was set, and\u003cbr\u003ethe daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any\u003cbr\u003euser able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the\u003cbr\u003eother daemon logs on every reachable node, which contain other tenants\u0027 topology names, owners and\u003cbr\u003econfiguration fragments.\u003cbr\u003e\u003cbr\u003eThe same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so\u003cbr\u003e`/listLogs` and `/searchLogs` returned every tenant\u0027s topology and worker log file names regardless of the\u003cbr\u003ecaller. That part is metadata only.\u003cbr\u003e\u003cbr\u003eThere was no configuration that closed either behaviour.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eMitigation\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eUpgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the\u003cbr\u003eworker log paths already used, and the listing endpoints filter by the requesting user.\u003cbr\u003e\u003cbr\u003eUsers who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the\u003cbr\u003edaemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eCredit\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.\u003cbr\u003e"
            }
          ],
          "value": "Description\n\nThe Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For\ndaemon logs those settings were not applied: the access decision combined the \"this is a daemon log\" flag\nwith the authorizer result in a way that discarded the authorizer\u0027s answer whenever the flag was set, and\nthe daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any\nuser able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the\nother daemon logs on every reachable node, which contain other tenants\u0027 topology names, owners and\nconfiguration fragments.\n\nThe same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so\n`/listLogs` and `/searchLogs` returned every tenant\u0027s topology and worker log file names regardless of the\ncaller. That part is metadata only.\n\nThere was no configuration that closed either behaviour.\n\nMitigation\n\nUpgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the\nworker log paths already used, and the listing endpoints filter by the requesting user.\n\nUsers who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the\ndaemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.\n\nCredit\n\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "moderate"
            },
            "type": "Textual description of severity"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862 Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-14T14:05:07.981Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/hqyj3spllmbj6vg9vmx29b1tjhzysdkl"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Apache Storm Logviewer: Log Access Controls Not Enforced by Logviewer",
      "x_generator": {
        "engine": "Vulnogram 1.0.3"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2026-82437",
    "datePublished": "2026-09-14T14:05:07.981Z",
    "dateReserved": "2026-08-29T10:35:33.225Z",
    "dateUpdated": "2026-09-14T19:54:36.871Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-82437\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2026-09-14T15:17:10.757\",\"lastModified\":\"2026-09-14T20:58:48.430\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Description\\n\\nThe Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For\\ndaemon logs those settings were not applied: the access decision combined the \\\"this is a daemon log\\\" flag\\nwith the authorizer result in a way that discarded the authorizer\u0027s answer whenever the flag was set, and\\nthe daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any\\nuser able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the\\nother daemon logs on every reachable node, which contain other tenants\u0027 topology names, owners and\\nconfiguration fragments.\\n\\nThe same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so\\n`/listLogs` and `/searchLogs` returned every tenant\u0027s topology and worker log file names regardless of the\\ncaller. That part is metadata only.\\n\\nThere was no configuration that closed either behaviour.\\n\\nMitigation\\n\\nUpgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the\\nworker log paths already used, and the listing endpoints filter by the requesting user.\\n\\nUsers who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the\\ndaemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.\\n\\nCredit\\n\\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.\"}],\"affected\":[{\"source\":\"security@apache.org\",\"affectedData\":[{\"vendor\":\"Apache Software Foundation\",\"product\":\"Apache Storm Logviewer\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://repo.maven.apache.org/maven2\",\"packageName\":\"org.apache.storm:storm-webapp\",\"versions\":[{\"version\":\"3.0.0\",\"lessThan\":\"3.1.0\",\"versionType\":\"semver\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":4.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":1.4}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-09-14T19:54:14.405653Z\",\"id\":\"CVE-2026-82437\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-862\"}]}],\"references\":[{\"url\":\"https://lists.apache.org/thread/hqyj3spllmbj6vg9vmx29b1tjhzysdkl\",\"source\":\"security@apache.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2026/09/13/16\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "vulnrichment": {
      "containers": "{\"cna\": {\"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2026-09-14T14:05:07.981Z\"}, \"title\": \"Apache Storm Logviewer: Log Access Controls Not Enforced by Logviewer\", \"problemTypes\": [{\"descriptions\": [{\"description\": \"CWE-862 Missing Authorization\", \"lang\": \"en\", \"cweId\": \"CWE-862\", \"type\": \"CWE\"}]}], \"source\": {\"discovery\": \"UNKNOWN\"}, \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Storm Logviewer\", \"collectionURL\": \"https://repo.maven.apache.org/maven2\", \"packageName\": \"org.apache.storm:storm-webapp\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.0.0\", \"lessThan\": \"3.1.0\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unaffected\"}], \"descriptions\": [{\"value\": \"Description\\n\\nThe Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For\\ndaemon logs those settings were not applied: the access decision combined the \\\"this is a daemon log\\\" flag\\nwith the authorizer result in a way that discarded the authorizer\u0027s answer whenever the flag was set, and\\nthe daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any\\nuser able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the\\nother daemon logs on every reachable node, which contain other tenants\u0027 topology names, owners and\\nconfiguration fragments.\\n\\nThe same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so\\n`/listLogs` and `/searchLogs` returned every tenant\u0027s topology and worker log file names regardless of the\\ncaller. That part is metadata only.\\n\\nThere was no configuration that closed either behaviour.\\n\\nMitigation\\n\\nUpgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the\\nworker log paths already used, and the listing endpoints filter by the requesting user.\\n\\nUsers who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the\\ndaemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.\\n\\nCredit\\n\\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.\", \"lang\": \"en\", \"supportingMedia\": [{\"type\": \"text/html\", \"base64\": false, \"value\": \"\u003cb\u003eDescription\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eThe Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For\u003cbr\u003edaemon logs those settings were not applied: the access decision combined the \\\"this is a daemon log\\\" flag\u003cbr\u003ewith the authorizer result in a way that discarded the authorizer\u0027s answer whenever the flag was set, and\u003cbr\u003ethe daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any\u003cbr\u003euser able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the\u003cbr\u003eother daemon logs on every reachable node, which contain other tenants\u0027 topology names, owners and\u003cbr\u003econfiguration fragments.\u003cbr\u003e\u003cbr\u003eThe same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so\u003cbr\u003e`/listLogs` and `/searchLogs` returned every tenant\u0027s topology and worker log file names regardless of the\u003cbr\u003ecaller. That part is metadata only.\u003cbr\u003e\u003cbr\u003eThere was no configuration that closed either behaviour.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eMitigation\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eUpgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the\u003cbr\u003eworker log paths already used, and the listing endpoints filter by the requesting user.\u003cbr\u003e\u003cbr\u003eUsers who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the\u003cbr\u003edaemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eCredit\u003c/b\u003e\u003cbr\u003e\u003cbr\u003eThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.\u003cbr\u003e\"}]}], \"references\": [{\"url\": \"https://lists.apache.org/thread/hqyj3spllmbj6vg9vmx29b1tjhzysdkl\", \"tags\": [\"vendor-advisory\"]}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"moderate\"}}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"credits\": [{\"lang\": \"en\", \"value\": \"The ASF using Claude Agents\", \"type\": \"finder\"}], \"x_generator\": {\"engine\": \"Vulnogram 1.0.3\"}}, \"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"http://www.openwall.com/lists/oss-security/2026/09/13/16\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2026-09-14T14:13:39.910Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 4.3, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"LOW\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-82437\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-09-14T19:54:14.405653Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-09-14T19:54:32.080Z\"}}]}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-82437\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"state\": \"PUBLISHED\", \"assignerShortName\": \"apache\", \"dateReserved\": \"2026-08-29T10:35:33.225Z\", \"datePublished\": \"2026-09-14T14:05:07.981Z\", \"dateUpdated\": \"2026-09-14T19:54:36.871Z\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…