CVE-2026-16211

LOWPre-NVD 2.62.6—
EchelonGraph scoreHIGH confidence

Score 2.6 from GitHub Security Advisory (severity: LOW) published 2026-07-19. a secondary CVSS source baseline 2.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
2.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability was determined in allegro up to bcf65b994ef29fb3fc2e10b660e6288723d5209e. This impacts the function AssetLastHostname.increment_hostname of the file src/ralph/assets/models/assets.py of the component Hostname Allocation Handler. Executing a manipulation of the argument counter can lead to race condition. Attacks of this nature are highly complex. The exploitability is said to be difficult. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
2.6
EG Score
2.6(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity26% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.3%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

References (5)

Vendor Advisories for CVE-2026-16211(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:05 UTCEG score recompute
  4. 2026-07-22 23:56 UTCEG score recompute
  5. 2026-07-22 23:56 UTCGHSA enrichment
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-20 20:41 UTCNVD updateCVSS v4 → 1.2
  9. 2026-07-20 19:12 UTCMITRE cvelistV5CVSS v4 → 2.1
  10. 2026-07-20 17:49 UTCEG score recompute
  11. 2026-07-20 17:49 UTCGHSA enrichment
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-19 04:23 UTCEG score recompute
  15. 2026-07-19 04:22 UTCNVD updateCVSS v4 → 1.2
  16. 2026-07-19 03:42 UTCEG score recompute
  17. 2026-07-19 03:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16211?
CVE-2026-16211 is a low vulnerability published on July 19, 2026. A vulnerability was determined in allegro up to bcf65b994ef29fb3fc2e10b660e6288723d5209e. This impacts the function AssetLastHostname.increment_hostname of the file src/ralph/assets/models/assets.py of the component Hostname Allocation Handler. Executing a manipulation of the argument counter can…
When was CVE-2026-16211 disclosed?
CVE-2026-16211 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16211 actively exploited?
CVE-2026-16211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-16211?
CVE-2026-16211 has a CVSS v3 base score of 2.6 (NVD).
How do I remediate CVE-2026-16211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16211

Explore →

Is Your Infrastructure Affected by CVE-2026-16211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs