The Hacker Wire@TheHackerWireDisclosure
The text announces CVE-2026-32633 and describes a specific API behavior that exposes raw server objects, but it does not provide exploitation details, a PoC, or patch information.
CyberDudeBivash® | Global Cybersecurity Company@cyberbivashDisclosure
The tweet announces CVE-2026-32633, identifying its impact on Glances' Browser API, but provides no PoC, exploit code, patch, or evidence of active exploitation.
Vulmon Vulnerability Feed@VulmonFeedsDisclosure
The tweet lists CVE‑2026‑32633 as an unauthenticated credential-exposure flaw in Glances, referencing a Vulmon details page but providing no PoC, exploit, patch, or evidence of active use.
CVE@CVEnewDisclosure
The statement announces CVE-2026-32633, noting that Glances before version 4.5.2 exposes raw server information via the `/api/4/serverslist` endpoint; no PoC, exploit, patch or active exploitation details are provided.
CVEFind.com@CveFindComDisclosure
A critical credential‑exposure vulnerability exists in Glances versions before 4.5.2, and updating to version 4.5.2 will address the flaw.
0day Signal@0dayPublishingDisclosure
The tweet announces CVE‑2026‑32633, highlighting credential leakage via mutated server objects and in‑memory state pollution, but offers no PoC, exploit details, patch information, or evidence of active exploitation.
PulsePatch.io@pulsepatchioDisclosure
The post announces CVE-2026-32633, detailing a credential exposure issue in Glances’ Browser API, with a link to an external write‑up but no PoC, exploit, or mitigation information.