golang.org/x/image: Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
Excessive memory allocation when decoding malicious SFNT in golang.org/x/image. GO-2026-4962, CVE-2026-33812.
osv.devquote checked- security advisory
- Your code14 things to find
Nemotron fixes
In its own wordsmatches the page ✓
Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
What Teire looks for in your code
- golang.org/x/image/font/sfnt.Collection.Font (go)
- golang.org/x/image/font/sfnt.Font.GlyphAdvance (go)
- golang.org/x/image/font/sfnt.Font.GlyphBounds (go)
- golang.org/x/image/font/sfnt.Font.GlyphIndex (go)
- golang.org/x/image/font/sfnt.Font.GlyphName (go)
- golang.org/x/image/font/sfnt.Font.Kern (go)
- golang.org/x/image/font/sfnt.Font.LoadGlyph (go)
- golang.org/x/image/font/sfnt.Font.Name (go)
- golang.org/x/image/font/sfnt.Font.WriteSourceTo (go)
- golang.org/x/image/font/sfnt.Parse (go)
- golang.org/x/image/font/sfnt.ParseCollection (go)
- golang.org/x/image/font/sfnt.ParseCollectionReaderAt (go)
- golang.org/x/image/font/sfnt.ParseReaderAt (go)
Does it reach your code?