Skip to content

Vendor

whisperfish vulnerabilities

5 published CVES affecting whisperfish, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
5
Critical
0
High
5
Medium
0
Low
0
Unscored
0
CISA KEV
0
Atom feed of whisperfish alerts

Products

Latest whisperfish CVEs

Newest publication first

  2. CVE-2025-24903 libsignal-service-rs Doesn't Check Origin of Sync Messages

    Published
    HighCVSS 8.5 EPSS 0.19%

    libsignal-service-rs is a Rust version of the libsignal-service-java library which implements the core functionality to communicate with Signal servers. Prior to commit 82d70f6720e762898f34ae76b0894b0297d9b2f8, any contact may forge a sync message, impersonating another device of...

  3. CVE-2024-39697 phonenumber panics on parsing crafted phonenumber inputs

    Published
    HighCVSS 8.6 EPSS 0.71%

    phonenumber is a library for parsing, formatting and validating international phone numbers. Since 0.3.4, the phonenumber parsing code may panic due to a panic-guarded out-of-bounds access on the phonenumber string. In a typical deployment of rust-phonenumber, this may get trigge...

  4. CVE-2023-42447 blurhash panics on parsing crafted inputs

    Published
    HighCVSS 7.5 EPSS 0.62%

    blurhash-rs is a pure Rust implementation of Blurhash, software for encoding images into ASCII strings that can be turned into a gradient of colors representing the original image. In version 0.1.1, the blurhash parsing code may panic due to multiple panic-guarded out-of-bounds a...

  5. CVE-2023-42444 phonenumber panics on parsing crafted RF3966 inputs

    Published
    HighCVSS 7.5 EPSS 0.87%

    phonenumber is a library for parsing, formatting and validating international phone numbers. Prior to versions 0.3.3+8.13.9 and 0.2.5+8.11.3, the phonenumber parsing code may panic due to a panic-guarded out-of-bounds access on the phonenumber string. In a typical deployment of r...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.