{"id":9811,"date":"2025-03-13T09:16:59","date_gmt":"2025-03-13T09:16:59","guid":{"rendered":"https:\/\/fusionmindlabs.com\/blogs\/meta-warns-of-freetype-vulnerability\/"},"modified":"2025-03-13T09:17:01","modified_gmt":"2025-03-13T09:17:01","slug":"meta-warns-of-freetype-vulnerability","status":"publish","type":"post","link":"https:\/\/fusionmindlabs.com\/blogs\/meta-warns-of-freetype-vulnerability\/","title":{"rendered":"Meta Warns of FreeType Vulnerability"},"content":{"rendered":"\n<\/p>\n
\n

\ue802<\/i>Mar 13, 2025<\/span>\ue804<\/i>Ravie Lakshmanan<\/span><\/span>Open Source \/ Vulnerability<\/span><\/p>\n<\/div>\n

\n
\n
\n<\/a>\n<\/div>\n

Meta has issued a warning about a security vulnerability affecting the FreeType<\/a> open-source font rendering library, which may have been exploited in the wild.<\/p>\n

The vulnerability, identified as CVE-2025-27363<\/strong><\/a>, has a CVSS score of 8.1, indicating a high level of severity. It is described as an out-of-bounds write flaw that can be exploited to achieve remote code execution when parsing specific font files.<\/p>\n

According to the company’s advisory<\/a>, “an out-of-bounds write exists in FreeType versions 2.13.0 and below when attempting to parse font subglyph structures related to TrueType GX and variable font files.” This occurs because the vulnerable code assigns a signed short value to an unsigned long and then adds a static value, causing it to wrap around and allocate too small of a heap buffer. As a result, the code writes up to 6 signed long integers out of bounds relative to this buffer, which may lead to arbitrary code execution.<\/p>\n

The company has not provided details on how the vulnerability is being exploited, the parties responsible, or the scope of the attacks. However, it has acknowledged that the bug “may have been exploited in the wild.”<\/p>\n

\"Cybersecurity\"<\/a><\/center><\/div>\n

When contacted, FreeType developer Werner Lemberg stated that a fix for the vulnerability has been available for almost two years. “FreeType versions larger than 2.13.0 are no longer affected,” Lemberg said.<\/p>\n

In a separate message<\/a> posted on the Open Source Security mailing list oss-security, it has been revealed that several Linux distributions are running an outdated version of the library, making them susceptible to the flaw. These distributions include:<\/p>\n