Vulnerability from cleanstart
Published
2026-07-30 07:10
Modified
2026-07-30 09:35
Summary
Security fixes in management-api-for-apache-cassandra-5.0 0.1.108-r0
Details

Package management-api-for-apache-cassandra-5.0 version 0.1.108-r0 fixes 8 vulnerabilities: ghsa-4g8c-wm8x-jfhw, ghsa-jq43-27x9-3v86, ghsa-25qh-j22f-pwp8, ghsa-389x-839f-4rhx, ghsa-3p8m-j85q-pgmj...


{
  "affected": [
    {
      "package": {
        "ecosystem": "Alpine",
        "name": "management-api-for-apache-cassandra-5.0"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.1.108-r0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.108-r0"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package management-api-for-apache-cassandra-5.0 version 0.1.108-r0 fixes 8 vulnerabilities: ghsa-4g8c-wm8x-jfhw, ghsa-jq43-27x9-3v86, ghsa-25qh-j22f-pwp8, ghsa-389x-839f-4rhx, ghsa-3p8m-j85q-pgmj...",
  "id": "CLEANSTART-2026-NP47613",
  "modified": "2026-07-30T09:35:13Z",
  "published": "2026-07-30T07:10:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/k8ssandra/management-api-for-apache-cassandra"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in management-api-for-apache-cassandra-5.0 0.1.108-r0",
  "upstream": [
    "ghsa-4g8c-wm8x-jfhw",
    "ghsa-jq43-27x9-3v86",
    "ghsa-25qh-j22f-pwp8",
    "ghsa-389x-839f-4rhx",
    "ghsa-3p8m-j85q-pgmj",
    "ghsa-5jpm-x58v-624v",
    "ghsa-xq3w-v528-46rv",
    "ghsa-fghv-69vj-qj49"
  ]
}



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…