ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-48611

In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check.

Published Mar 10, 2026 · catalog updated Jun 17, 2026 · In DeviceId of DeviceId.java,

Check if you run it

No confirmed exploitation is on record for CVE-2025-48611. EPSS is 0.20%. Act only if a listed version of In DeviceId of DeviceId.java, is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (In DeviceId of DeviceId.java,).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Advisory link
Affected products
cpe google/android

In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe google/androidversion unspecified

How to fix CVE-2025-48611

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-48611. EPSS is 0.20%. Act only if a listed version of In DeviceId of DeviceId.java, is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-120: Classic Buffer Overflow. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 10, 2026 · NIST NVD

    Detected

    In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  2. Jun 17, 2026 · NIST NVD

    Updated

    In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Sources

  • CVE.orgVulnerability recordCVE-2025-48611

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-48611

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2025-48611

    In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.