CVE-2025-47268

Exp

ping in iputils before 20250602 allows a denial of service (application error or incorrect data collection) via a crafted ICMP Echo Reply packet, because of a signed 64-bit integer overflow in timestamp multiplication.

Published: 2025-05-05 Last update: 2026-04-06 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-47268 is rated High Exploit Risk (63.8/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.51%). 3 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-47268

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-47268

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-07 0.91% 0.51% -0.40%
2 2026-03-01 0.33% 0.91% +0.58%
3 2026-01-27 — 0.33% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-47268

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2025-47268

OS Trackers for CVE-2025-47268

vendor priority summary link
alpine — CVE-2025-47268: 1 source package rows (iputils); 6 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 1, open 5. https://security.alpinelinux.org/vuln/CVE-2025-47268
debian unimportant CVE-2025-47268 unimportant priority: Debian including 1 source packages (iputils), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-47268
redhat medium — https://access.redhat.com/security/cve/CVE-2025-47268
suse medium CVE-2025-47268 severity moderate: SUSE including 266 source package names (13.2-9.2:curl-8.14.1-slfo.1.1_3.1, 13.2-9.2:iputils-20221126-slfo.1.1_2.1, …), 581 product×package rows across 322 product lines (Container suse/hpc/warewulf4-x86_64/sle-hpc-node, Container suse/manager/5.0/x86_64/server, … (322 product lines)): Fixed 360, Known Affected 221. https://www.suse.com/security/cve/CVE-2025-47268/
ubuntu low CVE-2025-47268 low priority: Ubuntu including 1 source packages (iputils), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 5, released 4, ignored 1. https://ubuntu.com/security/CVE-2025-47268

Affected software / configurations for CVE-2025-47268

Vendor Product Version Raw CPE
iputils iputils < 20250602 cpe:2.3:a:iputils:iputils:*:*:*:*:*:*:*:*

References for CVE-2025-47268

cvelogic Threat Intelligence