dbcve.org
InstagramApplication · Facebook

CVE-2020-1895

HIGH · 7.8 CVSS v3.1 Published 2020-04-09
Fix available
A fix is available. Upgrade to 128.0.0.26.128 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A large heap overflow could occur in Instagram for Android when attempting to upload an image with specially crafted dimensions. This affects versions prior to 128.0.0.26.128.

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 confidence

A heap overflow vulnerability exists in Instagram for Android versions prior to 128.0.0.26.128. The vulnerability is triggered when a user attempts to upload an image with specially crafted dimensions, causing a buffer overflow on the heap during image processing.

MitigationUpgrade Instagram for Android to version 128.0.0.26.128 or later from the Google Play Store. No code-level remediation is required as this is a consumer-facing mobile application vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InstagramApplication
Affected:< 128.0.0.26.128

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Instagram for Android is installed
    Open device Settings > Apps > Apps list and look for Instagram, or check via ADB: adb shell pm list packages | grep instagram
    Affected if Instagram for Android is not present on the device (not affected)
  2. Locate the installed version number
    In Settings > Apps > Instagram > App info, read the 'Version' field; or via ADB: adb shell dumpsys package com.instagram.android | grep versionName
    Affected if Unable to determine version (further investigation needed)
  3. Compare installed version to 128.0.0.26.128
    Compare the version string found in step 2 against 128.0.0.26.128 using standard version comparison (major.minor.patch format)
    Affected if Installed version is less than 128.0.0.26.128 (e.g., 127.0.0.26.125 or earlier)
  4. Verify no update has been applied
    Check if the Google Play Store shows a newer version available for Instagram, or attempt to check for updates in the Play Store app
    Affected if A newer version is available but not yet installed

If Instagram for Android is installed and the version is lower than 128.0.0.26.128, the device is vulnerable to this heap overflow during image upload processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 128.0.0.26.128 or later
Fixed in 128.0.0.26.128
Interim mitigation

Upgrade Instagram for Android to version 128.0.0.26.128 or later from the Google Play Store. No code-level remediation is required as this is a consumer-facing mobile application vulnerability.

Fix this in Instagram Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1895 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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