CVE-2025-50861
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Lotus Cars Android app (com.lotus.carsdomestic.intl) 1.2.8 contains an exported component, PushDeepLinkActivity, which is accessible without authentication via ADB or malicious apps. This poses a risk of unintended access to application internals and can cause denial of service or logic abuse.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Lotus Cars Android app version 1.2.8 contains an exported Activity component (PushDeepLinkActivity) that can be invoked without authentication by any other app installed on the device or via ADB. This exposes application internals to unauthorized external access, enabling potential denial of service through repeated component invocation or abuse of the deep linking logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Lotus Cars Android app is installedList installed packages using 'adb shell pm list packages | grep lotus' or check app settingsAffected if Package named 'com.lotuscars.app' or similar Lotus Cars package is present
-
Verify the app version is 1.2.8Run 'adb shell dumpsys package <package_name>' and look for versionName or versionCode in the package infoAffected if Version shows 1.2.8 specifically
-
Check if PushDeepLinkActivity exists and is exportedDecompile the APK and inspect AndroidManifest.xml for <activity android:name='.PushDeepLinkActivity'> and look for 'android:exported="true"' or an intent-filter without exported=falseAffected if PushDeepLinkActivity element has exported="true" or has an intent-filter with no exported="false" set
-
Verify the activity can be invoked externallyAttempt to launch via 'adb shell am start -n <package>/com.lotuscars.app.PushDeepLinkActivity' from a non-rooted context or a different app's intentAffected if Activity starts successfully without authentication or permission errors
You are affected if the Lotus Cars Android app version 1.2.8 is installed and its PushDeepLinkActivity component is exported (exported=true or has intent-filter without exported=false), allowing unauthorized external apps or ADB commands to trigger it.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the exported attribute on PushDeepLinkActivity in the AndroidManifest.xml, or implement proper authentication/permission checks within the activity to ensure only authorized callers can access the component.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50861 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data