Vulnerability from cleanstart
Published
2026-08-13 12:10
Modified
2026-08-14 05:57
Summary
Security fixes in argo-events 1.9.10-r1
Details

Package argo-events version 1.9.10-r1 fixes 17 vulnerabilities: ghsa-p77j-4mvh-x3m3, ghsa-hrxh-6v49-42gf, CVE-2026-33186, ghsa-mh2q-q3fh-2475, CVE-2026-29181...

References

{
  "affected": [
    {
      "package": {
        "ecosystem": "Alpine",
        "name": "argo-events"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.9.10-r1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.9.10-r1"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package argo-events version 1.9.10-r1 fixes 17 vulnerabilities: ghsa-p77j-4mvh-x3m3, ghsa-hrxh-6v49-42gf, CVE-2026-33186, ghsa-mh2q-q3fh-2475, CVE-2026-29181...",
  "id": "CLEANSTART-2026-ES11075",
  "modified": "2026-08-14T05:57:22Z",
  "published": "2026-08-13T12:10:09Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/argoproj/argo-events"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in argo-events 1.9.10-r1",
  "upstream": [
    "ghsa-p77j-4mvh-x3m3",
    "ghsa-hrxh-6v49-42gf",
    "CVE-2026-33186",
    "ghsa-mh2q-q3fh-2475",
    "CVE-2026-29181",
    "ghsa-qw64-3x98-g7q2",
    "ghsa-m3xc-h892-ggx6",
    "CVE-2026-44973",
    "CVE-2026-44740",
    "ghsa-crhj-59gh-8x96",
    "ghsa-w5pp-99ch-qj29",
    "ghsa-m7cr-m3pv-hgrp",
    "CVE-2026-45571",
    "CVE-2026-45570",
    "ghsa-q9hv-hpm4-hj6x",
    "CVE-2026-1229",
    "ghsa-gxhx-2686-5h9g"
  ]
}



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…