(CVE-2026-56860)
Vulnerability from cleanstart – Published: 2026-09-01 11:17 – Updated: 2026-09-18 11:59 – Source websitePackage prometheus-pushgateway-fips version 1.10.0-r3 fixes 44 vulnerabilities: CVE-2026-56860, CVE-2026-56858, CVE-2026-33818, CVE-2026-56853, CVE-2026-56859...
| URL | Type | |
|---|---|---|
{
"affected": [
{
"package": {
"ecosystem": "CleanStart",
"name": "prometheus-pushgateway-fips"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.10.0-r3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.10.0-r3"
]
}
],
"credits": [],
"database_specific": {},
"details": "Package prometheus-pushgateway-fips version 1.10.0-r3 fixes 44 vulnerabilities: CVE-2026-56860, CVE-2026-56858, CVE-2026-33818, CVE-2026-56853, CVE-2026-56859...",
"id": "CLEANSTART-2026-LT82827",
"modified": "2026-09-18T11:59:01.768079Z",
"published": "2026-09-01T11:17:16Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/prometheus/pushgateway"
}
],
"related": [],
"schema_version": "1.7.3",
"summary": "Security fixes in prometheus-pushgateway-fips 1.10.0-r3",
"upstream": [
"CVE-2026-56860",
"CVE-2026-56858",
"CVE-2026-33818",
"CVE-2026-56853",
"CVE-2026-56859",
"CVE-2026-56862",
"CVE-2026-42508",
"CVE-2025-47914",
"CVE-2025-58181",
"CVE-2026-39835",
"CVE-2026-46598",
"CVE-2026-39828",
"CVE-2025-22869",
"CVE-2025-47913",
"CVE-2026-39829",
"CVE-2026-46597",
"CVE-2024-45337",
"CVE-2026-39830",
"CVE-2026-39831",
"CVE-2026-39832",
"CVE-2026-39833",
"CVE-2026-39834",
"CVE-2026-46595",
"CVE-2026-39827",
"CVE-2025-22870",
"CVE-2024-45338",
"CVE-2025-22872",
"CVE-2025-47911",
"CVE-2025-58190",
"CVE-2026-25681",
"CVE-2026-27136",
"CVE-2026-33814",
"CVE-2026-46600",
"CVE-2026-39821",
"CVE-2026-42502",
"CVE-2026-42506",
"CVE-2025-22868",
"CVE-2026-42151",
"CVE-2026-42154",
"CVE-2026-56852",
"CVE-2026-25680",
"CVE-2026-44903",
"CVE-2026-40179",
"CVE-2026-39824"
],
"withdrawn": "2026-09-18T11:59:01.768079Z"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.