Vulnerability from cleanstart
Published
2026-07-30 07:10
Modified
2026-07-30 09:34
Summary
Security fixes in logstash-fips 9.2.4-r2
Details

Package logstash-fips version 9.2.4-r2 fixes 19 vulnerabilities: CVE-2025-61770, CVE-2025-61771, CVE-2025-61772, CVE-2025-61919, CVE-2025-61780...

References

{
  "affected": [
    {
      "package": {
        "ecosystem": "Alpine",
        "name": "logstash-fips"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.2.4-r2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "9.2.4-r2"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package logstash-fips version 9.2.4-r2 fixes 19 vulnerabilities: CVE-2025-61770, CVE-2025-61771, CVE-2025-61772, CVE-2025-61919, CVE-2025-61780...",
  "id": "CLEANSTART-2026-VQ54070",
  "modified": "2026-07-30T09:34:04Z",
  "published": "2026-07-30T07:10:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/elastic/logstash"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in logstash-fips 9.2.4-r2",
  "upstream": [
    "CVE-2025-61770",
    "CVE-2025-61771",
    "CVE-2025-61772",
    "CVE-2025-61919",
    "CVE-2025-61780",
    "CVE-2025-27219",
    "CVE-2025-27220",
    "CVE-2025-27221",
    "CVE-2025-61594",
    "CVE-2025-68161",
    "CVE-2025-67130",
    "CVE-2024-45993",
    "CVE-2025-31344",
    "CVE-2025-61726",
    "CVE-2025-61728",
    "CVE-2025-68121",
    "CVE-2026-22860",
    "CVE-2026-25765",
    "CVE-2026-25500"
  ]
}



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…