Explore tweets tagged as #Libxml2
🌐 Celebrating 25 years of Libxml2! 🎉 A testament to open-source success, yet challenges persist. 📉 While it powers so many sectors, support for its sustainability is lacking. #OpenSource #Libxml2 #CommunityMatters
0
0
0
in lxml <= 5.3.2 with libxml2 2.12.x, XXE using parameter entities was possible due to libxml2 behavior - allowing indirect overrides of local DTDs. this worked even without resolve_entities, since libxml2 expanded parameter entities anyway :). it didn’t really make noise since.
What happens when a Dojo challenge collides with a library update? 🔍. The Hex Color Palette challenge used to rely on a specific XXE flow – until lxml changed the rules. Find out why our latest Dojo report includes two different payloads and reports that leak the same flag via
0
1
30
The solo maintainer for libxml2 is no longer accepting embargoed vulnerability reports, citing the unsustainable burden as an unpaid volunteer. Security issues will be treated like any other bug report moving forward. 📄 #cybersecurity #opensource.
0
2
3
Four flaws in libxml2 (CVE-2025-6021, CVE-2025-49794, CVE-2025-49795, CVE-2025-49796) expose systems to memory corruption, RCE, and DoS attacks. #libxml2 #XMLSecurity #Cybersecurity #Vulnerability #MemoryCorruption.
0
1
0