Information Exposure in cordova-android

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2016-6799: 2.58% estimated exploitation activity in the next 30 days; percentile 85.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Versions of cordova-android prior to 6.0.0 are vulnerable to Information Exposure through log files. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications. Recommendation Upgrade to version 6.0.0 or later.

Published by the source

11 Sep 2020, 21:14 UTC

Last modified by the source

8 Nov 2023, 03:58 UTC

Source last checked

26 Oct 2026, 12:09 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gwpf-62xp-vrg6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gwpf-62xp-vrg6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-6799

Advisory: Information Exposure in cordova-android
IDs: CVE-2016-6799, GHSA-gwpf-62xp-vrg6
Record: https://patchnext.com/advisories/cve-2016-6799 (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cordova-android 6.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm cordova-android: affected < 6.0.0; fixed in 6.0.0

## Suggested inspection (read-only)
- `npm ls cordova-android --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cordova-android.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gwpf-62xp-vrg6 (OSV record GHSA-gwpf-62xp-vrg6 lists affected ranges: npm cordova-android >=0 <6.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-gwpf-62xp-vrg6 (GitHub-reviewed advisory GHSA-gwpf-62xp-vrg6 lists affected ranges: npm cordova-android >=0 <6.0.0)

Commands are suggestions: review each one before running it.