Skip to main content
No exploitation reportedFix available

CVE-2025-0078

No exploitation reported by the sources we read.

  • Published2025-08-26
  • WeaknessCWE-250

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In main of main.cpp, there is a possible way to bypass SELinux due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Timeline

dates in UTC
  1. 2025-08-2623:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-0078?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-0078?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Google android
BranchAffectedFixed in
12.0= 12.0no fix published
12.1= 12.1no fix published
13.0= 13.0no fix published
14.0= 14.0no fix published
15.0= 15.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As google_android, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Androidother versions: not affected
    Affected
    • = 15no fix stated
    • = 14no fix stated
    • = 13no fix stated
    • = 12Lno fix stated
    • = 12no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-08-26

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • platform/frameworks/nativeAndroidfrom 12:0 · fixed in 12:2025-03-01
  • platform/frameworks/nativeAndroidfrom 12L:0 · fixed in 12L:2025-03-01
  • platform/frameworks/nativeAndroidfrom 13:0 · fixed in 13:2025-03-01
  • platform/frameworks/nativeAndroidfrom 14:0 · fixed in 14:2025-03-01
  • platform/frameworks/nativeAndroidfrom 15-next:0 · fixed in 15-next:2025-03-01
  • platform/frameworks/nativeAndroidfrom 15:0 · fixed in 15:2025-03-01

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2025-08-26
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-7fj9-687g-h53c

Frequently asked questions

What is CVE-2025-0078?

In main of main.cpp, there is a possible way to bypass SELinux due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Is CVE-2025-0078 actively exploited?

Active exploitation of CVE-2025-0078 has not been confirmed. Its EPSS score was 0.3% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-0078?

CVE-2025-0078 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running platform/frameworks/native? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record