Skip to content
Heist/ feed
Back to feed
Medium

bep/imagemeta allows a potentially large memory allocation in PNG and WebP parsing

Type: advisorySources: OSV

bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. The buffer created for parsing metadata for PNG and WebP images was only bounded by their input data type, which could lead to potentially large memory allocation, and unreasonably high for image metadata. Before v0.11.0, If you didn't trust the input images, this could be abused to construct denial-of-service attacks. v0.11.0 added a 10 MB upper limit.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2025-32025
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 19:48 UTC · Revision 1

Source evidence

bep/imagemeta allows a potentially large memory allocation in PNG and WebP parsing

core-osv · Original source

Published 8 Apr 2025, 15:13 UTC

bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. The buffer created for parsing metadata for PNG and WebP images was only bounded by their input data type, which could lead to potentially large memory allocation, and unreasonably high for image metadata. Before v0.11.0, If you didn't trust the input images, this could be abused to construct denial-of-service attacks. v0.11.0 added a 10 MB upper limit.

osv:CVE-2025-32025
Complete source record
{
  "id": "0d5d1c28e0b26b99c785ece9218f146fec3ce3efebbf795dd502e4a01982ca4f",
  "url": "https://osv.dev/vulnerability/CVE-2025-32025",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "bep/imagemeta allows a potentially large memory allocation in PNG and WebP parsing",
    "summary": "bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. The buffer created for parsing metadata for PNG and WebP images was only bounded by their input data type, which could lead to potentially large memory allocation, and unreasonably high for image metadata. Before v0.11.0, If you didn't trust the input images, this could be abused to construct denial-of-service attacks. v0.11.0 added a 10 MB upper limit.",
    "evidence": "osv:CVE-2025-32025",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2025-32025",
      "aliases": [
        "CVE-2025-32025",
        "GHSA-fmhh-rw3h-785m",
        "GO-2025-3599"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/bep/imagemeta",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "ee0de9b029f4e82106729f69559f27c9a404229d"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "v0.11.0"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "fixed": "ee0de9b029f4e82106729f69559f27c9a404229d"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  },
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "0.11.0"
                      }
                    ],
                    "source": "DESCRIPTION"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v0.10.0",
            "v0.9.0",
            "v0.8.4",
            "v0.8.3",
            "v0.8.2",
            "v0.8.1",
            "v0.8.0",
            "v0.7.6",
            "v0.7.5",
            "v0.7.4",
            "v0.7.3",
            "v0.7.2",
            "v0.7.1",
            "v0.7.0",
            "v0.6.0",
            "v0.5.0",
            "v0.4.0",
            "v0.3.0",
            "v0.2.0",
            "v0.1.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-32025.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:51.705043465Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/32xxx/CVE-2025-32025.json",
        "https://github.com/bep/imagemeta/security/advisories/GHSA-fmhh-rw3h-785m",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-32025",
        "https://github.com/bep/imagemeta/commit/ee0de9b029f4e82106729f69559f27c9a404229d"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-770"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/32xxx/CVE-2025-32025.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-32025",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 520253,
  "published_at": "2025-04-08T15:13:24.77+00:00"
}