sedem dni za posodobitev drugih, neizpostavljenih sistemov;

V pravljici!

[FIskalnaFinta2]
> sedem dni za posodobitev drugih, neizpostavljenih sistemov;

V pravljici!

Itak - URSIV je urad,kjer pametujejo in pisarijo, večinoma o zadevah ki jih bolj malo razumejo.
Notranji neizpostavljeni sistemi niso tak grozen problem, kar pa je odprto navzven, pa je vse prej kot hec.

[AlojzFerluga]
Notranji neizpostavljeni sistemi niso tak grozen problem, kar pa je odprto navzven, pa je vse prej kot hec.

sploh ce se znajdes iz oci v oci z razlikami med tem, kaj kot fatal error jemlje php 7 in kaj 8 :)

(flikal vceraj par srednje-kameno-dobnih serverjev, nima zveze s financami)

ŽE izkoriščajo? Ste mislili napisati ŠE? In še naprej jih bodo.

"Ranljivost PHP je (torej) bila poznana NSA. Verjetno zato, ker jo je NSA vgradila tja ..." (Niso moje besede.)

The patch was supposed to release on October 22nd, ⚠️but someone leaked it early on October 20th, and then the NSA released their advisory. The coordinated disclosure was planned for Thursday, October 22 Someone leaked details on October 20 (two days early) PHP moved the patch to October 21 (one day earlier than even the moved date) NSA released advisory on October 21 👀👀🚨🚨

The NSA didn't wait for the official patch to be released before publishing their advisory. They were ready to go the moment the leak happened.🚨

This means the NSA already had the advisory written before the leak. They were prepared. They knew about this vulnerability before the public discovery.
🚨
Not only this The NSA typically doesn't issue public advisories about PHP vulnerabilities. They focus on classified systems.🚨

The fact that they're issuing a public advisory about a web vulnerability suggests they're using this as a pretext for something larger.

Someone who was part of the coordinated disclosure process leaked the details to force the PHP team to release the patch early. This person wanted the patch out before the original Thursday embargo.🚨

Whats even more unusual is that Gemini 4 Argon found it too. This means multiple AI systems (OpenAI's Patch the Planet and Google's Gemini 4 Argon) independently found the same vulnerability.
🚨
Wiz is a subsidiary of Alphabet Inc., which is Google.

Now look at the overlap. Calif used OpenAI's GPT-5.6 Sol.

But Amazon Threat Intelligence identified a PHP2Shell exploitation attempt dating back to October 17, 2026, four days before public disclosure. This means a hostile actor had already found and was exploiting the vulnerability before the "independent discovery" was publicly announced. The intelligence community likely detected this exploitation through signals intelligence or threat hunting. They realized the bug was burned. A hostile actor was already in.🚨👀

Intelligence services (likely the NSA, given their rapid response) had this exploit in their library. AI vulnerability scanners were getting close to finding it independently. To prevent a hostile intelligence service from finding it first and weaponizing it, the NSA and allied intelligence services coordinated a controlled burn operation. 🚨👀

Imo they used Google (Wiz) and OpenAI (Calif) as cutouts to create the appearance of independent discovery. This provides cover for the intelligence community: "AI found it, we didn't hoard it, we're just responding to a new discovery."

🚨👀Basically the era of intelligence services hoarding vulnerabilities is over. AI is finding them all. This PHP vulnerability is the first public casualty of the AI-driven vulnerability discovery race.


www.huntress.com/blo...rabilities

www.nsa.gov/Press-Ro...abilities/

www.aikido.dev/blog/...-php2shell