@JenovaSPARK @NWBroJaneway

JUST IN: 🇧🇷 Over $200,000,000,000 wiped out from the Brazil stock market at open after Lula da Silva wins Brazil's presidential election, defeating Flávio Bolsonaro.

🤪 TELL ME YOUR WACKY HACKER NAME First Name: your IP Address Middle Name: username Last Name: that WACKY private key (PEM format)

Hey @grok, Make me a pie chart of what my 𝕏 content consists of. Thanks

BBC: Hablaremos con nuestro experto en seguridad de BBC respecto a la vulnerabilidad de PHP. El experto en seguridad: No sabía que PHP existía hasta ayer en la mañana.

CVE-2026-81983: Integer overflow leads to an out-of-bounds write in Adobe Acrobat Read on dbugs: dbu.gs/news/cve-2026-81983-i… Remedio researchers discovered CVE-2026-81983 (dbu.gs/vulnerability/CVE-202…) in Adobe Acrobat's image-processing pipeline. The vulnerability is triggered by opening a PDF containing a specially crafted 16-bit image and can cause an out-of-bounds write in "Acrobat.dll". The flaw lies in a function that normalizes 16-bit image samples before compositing. The byte-swapping loop uses the product of the image width and the number of components as its iteration count, without checking it against the buffer size. Meanwhile, the buffer-size check calculates the required data length as "Width × components × 2", using the same 32-bit arithmetic. A CMYK image with a width of "0x20000000" is sufficient to trigger the vulnerability. The product "4 × 0x20000000" yields "0x80000000". Multiplying this by two during the size check causes the 32-bit result to wrap to zero, allowing an image data stream containing just 8 bytes to pass validation. The byte-swapping loop then uses the original iteration count of "0x80000000", advancing through memory two bytes at a time. The minimized trigger is a 745-byte PDF containing a single image row. The loop reads and writes beyond a 16-byte buffer, with the observed access violation occurring approximately 144 KB beyond the buffer's start. The vulnerable code is part of the 16-bit sample normalization routine, which swaps the bytes of each value directly in the source buffer. Whether this branch executes depends in part on the "keepEndian" flag. The minimal trigger uses an image XObject with "/BitsPerComponent 16", "/ColorSpace /DeviceCMYK", a height of 1, and a width of "0x20000000". Adobe fixed the vulnerability by introducing a 64-bit range check and rejecting sample counts greater than "INT_MAX". The fix was published in security bulletin APSB26-141 on September 8, 2026. The fixed versions are Acrobat / Acrobat Reader Continuous "26.002.21901" and Acrobat 2024 Classic "24.001.30429". Article: remedio.io/blog/cve-2026-819… CVE-2026-81983 — PT-2026-88482: dbu.gs/vulnerability/PT-2026…

An urgent notice from the Railway team blog.railway.com/p/security-…

So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.