CVE-2026-77298 (GCVE-0-2026-77298)
Vulnerability from cvelistv5
Published
2026-08-26 21:16
Modified
2026-08-27 14:17
CWE
  • CWE-863 - Incorrect Authorization
Summary
SeaweedFS is a distributed storage system for files and blobs. In versions 4.39 and earlier, the S3 API accepts an external OIDC JWT sent directly in the Authorization header and maps it to an IAM role without enforcing that role's trust policy, so a federated user can assume a role they are not permitted to hold. The standard STS AssumeRoleWithWebIdentity path rejects such a token when the role's trust policy does not trust the token's federated provider, but the direct S3 bearer path validates only the token itself and then authenticates as the mapped role and evaluates that role's attached S3 permissions. As a result, a valid OIDC user whose token would be denied the role through STS can obtain the role's S3 access, including object read, write, and delete, by presenting the raw OIDC JWT directly to the S3 API. This issue is fixed in version 4.40
Impacted products
Vendor Product Version
seaweedfs seaweedfs Version: < 4.40
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-77298",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-27T14:15:16.923624Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-27T14:17:48.966Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "seaweedfs",
          "vendor": "seaweedfs",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 4.40"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "SeaweedFS is a distributed storage system for files and blobs. In versions 4.39 and earlier, the S3 API accepts an external OIDC JWT sent directly in the Authorization header and maps it to an IAM role without enforcing that role\u0027s trust policy, so a federated user can assume a role they are not permitted to hold. The standard STS AssumeRoleWithWebIdentity path rejects such a token when the role\u0027s trust policy does not trust the token\u0027s federated provider, but the direct S3 bearer path validates only the token itself and then authenticates as the mapped role and evaluates that role\u0027s attached S3 permissions. As a result, a valid OIDC user whose token would be denied the role through STS can obtain the role\u0027s S3 access, including object read, write, and delete, by presenting the raw OIDC JWT directly to the S3 API. This issue is fixed in version 4.40"
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-863",
              "description": "CWE-863: Incorrect Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-26T21:16:51.165Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-757h-cm9x-wprg",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-757h-cm9x-wprg"
        },
        {
          "name": "https://github.com/seaweedfs/seaweedfs/commit/ac524e140a37242b2488be9dfffae918da1d4de1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/seaweedfs/seaweedfs/commit/ac524e140a37242b2488be9dfffae918da1d4de1"
        }
      ],
      "source": {
        "advisory": "GHSA-757h-cm9x-wprg",
        "discovery": "UNKNOWN"
      },
      "title": "SeaweedFS S3 OIDC Bearer authentication bypasses IAM role trust policy"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-77298",
    "datePublished": "2026-08-26T21:16:51.165Z",
    "dateReserved": "2026-08-20T19:17:14.375Z",
    "dateUpdated": "2026-08-27T14:17:48.966Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"cna\": {\"title\": \"SeaweedFS S3 OIDC Bearer authentication bypasses IAM role trust policy\", \"source\": {\"advisory\": \"GHSA-757h-cm9x-wprg\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV4_0\": {\"version\": \"4.0\", \"baseScore\": 8.7, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"NONE\", \"privilegesRequired\": \"LOW\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"HIGH\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"HIGH\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"HIGH\"}}], \"affected\": [{\"vendor\": \"seaweedfs\", \"product\": \"seaweedfs\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 4.40\"}]}], \"references\": [{\"url\": \"https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-757h-cm9x-wprg\", \"name\": \"https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-757h-cm9x-wprg\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/seaweedfs/seaweedfs/commit/ac524e140a37242b2488be9dfffae918da1d4de1\", \"name\": \"https://github.com/seaweedfs/seaweedfs/commit/ac524e140a37242b2488be9dfffae918da1d4de1\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"SeaweedFS is a distributed storage system for files and blobs. In versions 4.39 and earlier, the S3 API accepts an external OIDC JWT sent directly in the Authorization header and maps it to an IAM role without enforcing that role\u0027s trust policy, so a federated user can assume a role they are not permitted to hold. The standard STS AssumeRoleWithWebIdentity path rejects such a token when the role\u0027s trust policy does not trust the token\u0027s federated provider, but the direct S3 bearer path validates only the token itself and then authenticates as the mapped role and evaluates that role\u0027s attached S3 permissions. As a result, a valid OIDC user whose token would be denied the role through STS can obtain the role\u0027s S3 access, including object read, write, and delete, by presenting the raw OIDC JWT directly to the S3 API. This issue is fixed in version 4.40\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-863\", \"description\": \"CWE-863: Incorrect Authorization\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-08-26T21:16:51.165Z\"}}, \"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-77298\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-08-27T14:15:16.923624Z\"}}}], \"providerMetadata\": {\"shortName\": \"CISA-ADP\", \"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"dateUpdated\": \"2026-08-27T14:17:41.177Z\"}}]}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-77298\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-26T21:16:51.165Z\", \"dateReserved\": \"2026-08-20T19:17:14.375Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-08-26T21:16:51.165Z\", \"assignerShortName\": \"GitHub_M\"}",
      "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…