Quick answers
- Is CVE-2025-3654 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-3654 being exploited in the wild.
- How severe is CVE-2025-3654?
- Medium severity, with a CVSS score of 5.3, published 4 January 2026.
- Which products and versions are affected?
- Petlibro Smart Pet Feeder Platform up to 1.7.31.
- Is there a fix for CVE-2025-3654?
- A patch was published on 2025-12-04: Vendor claimed majority of issues resolved in latest app version Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-3654 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-3654?
- Check whether you run Petlibro or Petlibro Smart Pet Feeder Platform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An information disclosure vulnerability exists in the Petlibro Smart Pet Feeder Platform API due to improper authorization checks. Specifically, the /device/devicePetRelation/getBoundDevices endpoint allows unauthenticated attackers to retrieve sensitive hardware identifiers, such as device serial numbers and MAC addresses, by supplying a pet ID. Because subsequent device control APIs rely on these serial numbers for identification without verifying ownership, an attacker can leverage this disclosed information to achieve unauthorized control over the pet feeder, including modifying feeding schedules and accessing camera streams. The vendor has reportedly introduced a fix in later versions, though some legacy endpoints remained active during the disclosure process.
Affected products
- Petlibro Smart Pet Feeder Platform up to 1.7.31
Timeline
- 2025-11-05: disclosed: Initial report to vendor by security researcher
- 2025-12-04: patched: Vendor claimed majority of issues resolved in latest app version
- 2026-01-03: advisory: CVE published by VulnCheck