{
  "fix": "RHSA-2026:18162",
  "url": "https://patchblox.com/security/fix/linux/rhsa-2026-18162",
  "summary": "RHSA-2026:18162, released July 22, 2025, fixes 1 CVE in iputils (version 20240905-5.el10). None of them is reported as exploited. Patch Radar priority: Routine.",
  "platform": "linux",
  "type": "advisory",
  "title": "iputils security update",
  "released": "2025-07-22T00:00:00Z",
  "priority": "Routine",
  "priorityTier": 4,
  "priorityReason": "Closes CVE-2025-48964",
  "supported": true,
  "cveCount": 1,
  "exploitedCveCount": 0,
  "kevCveCount": 0,
  "ransomwareCveCount": 0,
  "maxEpss": 0.00404,
  "maxCvss": 6.5,
  "vendorAdvisory": "https://access.redhat.com/errata/RHSA-2026:18162",
  "appliesTo": [
    {
      "product": "iputils",
      "productUrl": "https://patchblox.com/security/product/linux/iputils",
      "release": "RHEL 10",
      "fixedVersion": "20240905-5.el10",
      "supported": true
    }
  ],
  "cves": [
    {
      "cveId": "CVE-2025-48964",
      "url": "https://patchblox.com/security/cve/CVE-2025-48964",
      "title": "ping in iputils before 20250602 allows a denial of service (application error in adaptive ping mode or incorrect data collection) via a crafted ICMP Echo Reply packet, because a zero timestamp can lead to large intermediate values that have an integer overflow when squared during statistics calculations. NOTE: this issue exists because of an incomplete fix for CVE-2025-47268 (that fix was only about timestamp calculations, and it did not account for a specific scenario where the original timestamp in the ICMP payload is zero).",
      "priority": "Routine",
      "severity": "Low",
      "cvss": 6.5,
      "epss": 0.00404,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    }
  ],
  "dataAsOf": "2026-11-07T12:40:37Z"
}