ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “credential disclosure”

313 stories

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllVulnerability 576Malware 285Ransomware 280Exploit / PoC 249Data breach 196Threat actor 102Phishing & fraud 71Policy & legal 38AI safety & security 25Industry 17Advisory 15Research 10AI tools & infra 7Model release 2
SeverityAllcritical 875high 609medium 313low 44info 36

CVE-2026-82434: Apache Storm Nimbus, Apache Storm Client: Disclosure of the Topology ZooKeeper Credential to Read-Only Users and to Logs

Apache Storm Nimbus and Client expose ZooKeeper topology credentials to read-only users and logs, fixed in 3.1.0.

CVE-2026-82434 affects Apache Storm Nimbus (storm-server) and Storm Client (storm-client) versions 3.0.0 before 3.1.0. When ZooKeeper authentication is configured, Storm retains storm.zookeeper.topology.auth.payload in the topology configuration because workers need it, but Nimbus serves that configuration verbatim to callers holding only read-only access. The credential also leaks into logs.

oss-securityupdated · 2d agofirst · 3d agoVulnerability 2 sourcesCVE-2026-824342· 1 read

Microsoft Teams for Android Vulnerability Exposes Sensitive Information

Microsoft patched CVE-2026-65812 in Teams for Android, an information-disclosure flaw that can leak credentials under specific conditions.

Microsoft fixed CVE-2026-65812, rated Important, which can insert sensitive information such as credentials into data sent by Microsoft Teams for Android (build 1416/1.0.0.2026133602). Exploitation is remote and low-complexity, requires low privileges plus user interaction, and impact is limited to high confidentiality impact. Microsoft says exploitation is less likely, with no public PoC, disclosure, or in-the-wild exploitation; the fix ships via the Teams app update on Google Play. Ofek Levin of Enclave reported the flaw through coordinated vulnerability disclosure.

Cyber Security News · 7d agoVulnerabilityCVE-2026-658121

NextGen Healthcare Mirth Connect

CISA warns NextGen Healthcare Mirth Connect <=4.7.1 has SQL injection and XXE flaws enabling credential theft, file writes, and DoS.

CISA released advisory ICSMA-26-253-01 covering three vulnerabilities in NextGen Healthcare Mirth Connect versions 4.7.1 and earlier: SQL injection CVE-2026-82583 (CVSS 8.3), XXE CVE-2026-78224 (CVSS 8.2), and XXE CVE-2026-82578 (CVSS 7.5). Exploitation could expose stored credentials for connected systems, enable arbitrary file writes, and cause denial-of-service conditions. No public exploitation has been reported; the product is deployed worldwide in the Healthcare and Public Health sector.

CISA Advisoriesupdated · 5d agofirst · 6d agoAdvisory 2 sourcesCVE-2026-82583CVE-2026-78224CVE-2026-82578

Veradigm Confirms Patient Data Exposed in Third-Party Data Breach

Veradigm disclosed a third-party vendor breach exposing patient data including Social Security numbers via stolen vendor API credentials.

Veradigm filed an 8-K with the SEC on September 8, 2026, disclosing that attackers used credentials stolen from a third-party vendor to access a specific vendor-facing API and download patient personal data, including Social Security numbers for some individuals. No clinical or medical information was compromised, and Veradigm's internal infrastructure was not breached directly. The company activated incident response, notified law enforcement, and is offering credit monitoring to affected individuals.

Cyber Security News · 7d agoData breach in the wild

CenterPoint Energy Confirms Data Breach Exposing Customers’ Personal Information

CenterPoint Energy confirmed an unauthorized third party accessed customer personal data via an external system, disclosed in an SEC Form 8-K filing.

CenterPoint Energy disclosed in a September 14, 2026 Form 8-K that an unauthorized third party obtained personal information of some customers through one of the company's external systems. The company learned of the incident after an online post claimed possession of a customer dataset, then activated incident-response protocols and engaged external forensic specialists. Electric and gas delivery operations were unaffected and the company does not expect a material financial impact, though response, notification, and compliance costs are being incurred. The number of affected customers, data types, and threat actor remain undisclosed as the investigation continues.

GBHackersupdated · 3h agofirst · 7h agoData breach 5 sources

Harley-Davidson Alleged Breach – CL0P Ransomware Adds Motorcycle Maker to the List

CL0P ransomware group listed Harley-Davidson on its extortion leak site, claiming a compromise; the motorcycle maker has not confirmed any breach.

The CL0P ransomware operation added Harley-Davidson to its public extortion portal, a listing highlighted by the ransomNews monitoring account on September 10, 2026. Harley-Davidson has not confirmed any compromise, and the initial access method, affected business unit, timing, and volume of stolen data remain unknown, with no sample files or technical indicators published. The article stresses that leak-site listings alone do not confirm a breach and can serve as negotiation pressure in double-extortion schemes. If verified, stolen data could fuel downstream phishing, BEC, credential-stuffing, and invoice fraud targeting dealers, suppliers, and customers.

Cyber Security News · 5d agoRansomware