Skip to content

LibPNG vulnerabilities via Flutter dependency #181669

Closed

Description

@matheusmourafpf

Hello,
A security scan on a mobile application identified multiple vulnerabilities affecting the LibPNG library.

Affected CVEs:

  • CVE-2025-64720
  • CVE-2025-65018
  • CVE-2025-66293
  • CVE-2026-22801

These vulnerabilities are related mainly to out-of-bounds read/write, heap buffer overflow, and integer truncation issues during PNG image parsing and processing.

Current situation:

  • The application uses LibPNG version 1.6.43
  • Security scanners report that LibPNG < 1.6.54 is affected by the CVEs listed above
  • Image decoding relies on LibPNG for PNG parsing and processing
  • LibPNG is not installed in our app; it is included indirectly as a dependency of the Flutter framework (through its underlying graphics stack).
  • The LibPNG version cannot be updated independently by the application, as it is managed by Flutter and its native dependencies

Impact and Severity:

  • The vulnerabilities may lead to:

    • Application crash (Denial of Service)
    • Memory corruption
    • Potential code execution in specific exploitation scenarios
  • Exploitation generally requires processing of crafted PNG image files

  • The attack vector is remote, with user interaction required (loading a malicious PNG)

  • Severity ranges from MEDIUM to HIGH, depending on the CVE and execution context

  • No widespread public exploits are currently known for these CVEs, but exploitation is technically feasible

Questions:

  • Is there a planned update of the Flutter Engine that includes a LibPNG version equivalent to or newer than upstream 1.6.54, addressing the listed CVEs?
  • Given that LibPNG is an internal Flutter dependency and cannot be updated independently by the application, what is the recommended remediation strategy to address these CVEs?
  • Are there any official mitigations or configuration recommendations that can be applied at application or framework level until an updated Flutter Engine is available?

References:

Activity

  1. crackedhandle commented on Jan 29, 2026

    @crackedhandle
    Contributor

    Thanks for reporting this.

    As you said, Flutter uses libpng inside the engine, so app developers can’t update it themselves. The fix has to come from a Flutter Engine update.

    Current situation

    • Apps using Flutter are affected because they indirectly use this libpng.
    • There is no way to upgrade libpng from the app side.

    Temporary safety tips

    • Avoid loading PNG images from unknown or untrusted sources.
    • If possible, make the server re-process or re-encode images before sending them to the app.

    Real fix needed

    • The Flutter team needs to update libpng in the engine to a safe version and release it.

    Could the Flutter team please tell:

    • Is an engine update planned for this?
    • In which release (stable / beta / dev) will this be fixed?

    Thanks.

  2. stuartmorgan-g commented on Jan 29, 2026

    @stuartmorgan-g
    Contributor

    The first three were resolved by #180712, but the last one is newer than that roll.

    /cc @jason-simmons FYI since you just did the last roll.

  3. stuartmorgan-g commented on Jan 29, 2026

    @stuartmorgan-g
    Contributor

    Ah, I didn't notice the existing issue covering the last CVE in this list.

  4. github-actions commented on Feb 12, 2026

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  5. locked as resolved and limited conversation to collaborators on Feb 12, 2026
  6. added a commit that references this issue on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    engineflutter/engine related. See also e: labels.team-engineOwned by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions