Vulnerability from cleanstart
Published
2026-07-30 07:10
Modified
2026-07-30 09:32
Summary
Security fixes in tempo-fips 2.9.1-r0
Details

Package tempo-fips version 2.9.1-r0 fixes 20 vulnerabilities: CVE-2026-33186, CVE-2025-47914, CVE-2025-58181, CVE-2025-47913, CVE-2026-32287...

References

{
  "affected": [
    {
      "package": {
        "ecosystem": "Alpine",
        "name": "tempo-fips"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.9.1-r0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.9.1-r0"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package tempo-fips version 2.9.1-r0 fixes 20 vulnerabilities: CVE-2026-33186, CVE-2025-47914, CVE-2025-58181, CVE-2025-47913, CVE-2026-32287...",
  "id": "CLEANSTART-2026-AY71406",
  "modified": "2026-07-30T09:32:26Z",
  "published": "2026-07-30T07:10:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/grafana/tempo"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in tempo-fips 2.9.1-r0",
  "upstream": [
    "CVE-2026-33186",
    "CVE-2025-47914",
    "CVE-2025-58181",
    "CVE-2025-47913",
    "CVE-2026-32287",
    "CVE-2025-11065",
    "CVE-2026-40179",
    "CVE-2026-32280",
    "CVE-2026-32281",
    "CVE-2026-32282",
    "CVE-2026-32283",
    "CVE-2026-32288",
    "CVE-2026-32289",
    "CVE-2026-33810",
    "ghsa-p77j-4mvh-x3m3",
    "ghsa-65xw-vw82-r86x",
    "ghsa-j5w8-q4qc-rx2x",
    "ghsa-f6x5-jh6r-wrfv",
    "ghsa-2464-8j7c-4cjm",
    "ghsa-vffh-x6r8-xx99"
  ]
}



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…