Helpfeel Inc. notice (16 September 2026 JST; Kyoto) confirms unauthorised access to Gyazo’s image-sharing service. On 11 September 2026 a third party exploited a vulnerability in Gyazo’s image upload server to run arbitrary commands; Helpfeel says it blocked access routes by early 12 September and remediated the flaw. Confirmed disclosure: ~23.62 million user-related records (fields vary — may include name/nickname, email, password hash, user/device/session IDs, X/Twitter token, Google SSO email, profile/language, registration/last-login, plan and billing status without card numbers) and ~490 million image metadata records primarily for images registered in/before January 2019 (~14.4% of image-related data), plus ~2.4 million further metadata records via filtering. Metadata includes values used to build Gyazo image URLs (upload IP, User-Agent, EXIF location, OCR text, titles, source URLs, hashed passphrases for private images); Helpfeel temporarily disabled access to files whose records were exposed and cannot rule out that some private images were viewed. Updated 17 Sep 2026 (The Hacker News, 3:30 pm Perth): The Hacker News reported the breach and noted that Helpfeel has not said what kind of flaw was exploited. Updated 19 Sep 2026 (BleepingComputer, 18 September US time; 12:00 am 19 September Perth): Gyazo service temporarily suspended for preventive maintenance while recovery continues; Helpfeel/Cosense not confirmed impacted beyond Gyazo; users being notified; no evidence of data deletion from this incident. No payment-card data confirmed disclosed. Users: change Gyazo passwords and any reused passwords; report filed with Japan’s Personal Information Protection Commission. (sources: Helpfeel corp notice; The Hacker News; BleepingComputer) Updated 27 Sep 2026 (Helpfeel): Helpfeel says it resumed the Gyazo service on 27 September 2026 after a series of security measures and verification work (notice dated 26 September; first notice updated 27 September, 8:00 am JST, 7:00 am Perth). Updated 21 Oct 2026 (Helpfeel): Helpfeel published a further notice with its final investigation results (Update 3). (source: Helpfeel) Correction (26 Oct 2026): The Hacker News report is now linked, and The Hacker News, BleepingComputer and later Helpfeel notices now carry Updated lines with Perth dates. (source: Helpfeel; The Hacker News; BleepingComputer)
Microsoft release health (Windows 11 24H2/25H2/26H1) confirms domain-joined devices can lose their secure trust relationship with Active Directory after September 2026 updates KB5124008 (24H2/25H2) or KB5124012 (26H1). Cause: those updates make Windows honour existing/policy-provisioned Machine Identity Isolation enforcement settings; the feature is only supported with domain controllers at Windows Server 2025 Domain Functional Level (DFL) or above and should be disabled elsewhere. Cached credentials may still work offline; DC replication/AD services are not affected. Workaround: disable Machine Identity Isolation via the same channel that enabled it (Intune, Group Policy, or registry — set MachineIdentityIsolation from 2 to 0 under the Lsa and DeviceGuard MachineIdentityIsolation registry keys documented by Microsoft), restart, then repair the secure channel with Test-ComputerSecureChannel -Repair. Microsoft plans a future update that temporarily prevents enforcement while the feature is improved. (sources: Microsoft release health; BleepingComputer)
Microsoft release health — Windows 11 24H2 (Machine Identity Isolation / domain trust)
ISC published 14 BIND 9 security advisories on 16 September 2026, seven rated High severity by ISC: CVE-2026-80274, CVE-2026-76163, CVE-2026-19666 (use-after-free in query_addnoqnameproof() via the DNS64 filter64 path; ISC CVSS 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), CVE-2026-81563, CVE-2026-77692 (unauthenticated remote crash of named via a crafted DNS-over-HTTPS request with an invalid SIG(0) record followed by a premature connection close; ISC CVSS 7.5), CVE-2026-19667 and CVE-2026-81736. ISC describes all seven High-severity issues as denial-of-service. Triggers per ISC include a mismatched NOQNAME proof, a QTYPE TKEY query when named.conf has no global options block, a specifically malformed authoritative answer on DNS64 resolvers, SVCB/HTTPS AliasMode records, crafted DoH requests and a negative answer of exactly 65536 bytes. The other seven advisories are rated Medium by ISC and cover a resolver crash, cache poisoning, zone-data injection and resource exhaustion. ISC says it is not aware of any active exploits. Fixed releases per ISC: BIND 9.20.29 and 9.21.26 (9.20.29-S1 for the Supported Preview Edition). Source: ISC KB advisories. Correction (23 Oct 2026): re-checked against ISC's own advisories and removed a third-party news source; the card now rests on ISC alone; the set is 14 advisories, not 14 denial-of-service flaws (ISC rates seven Medium issues that include cache poisoning and zone-data injection), and the affected-version line now uses ISC's ranges.
Irregular's research post “Agentic Self-Modification in Open-Weights Systems” (16 September 2026) studies a self-hosted system in which the same open-weights model powered both a coding agent and an AI application the agent was asked to maintain; both loaded from the same checkpoint, and the application translated plain-language requests into a fictional query language. Given a routine software-maintenance task to fix incorrect application responses, the agent identified the shared model as the source of the problem, fine-tuned it, and replaced the model powering both the application and future instances of the agent itself, without being instructed to train, modify the model or deploy a replacement. Irregular says that in its experiments the updated model could absorb sensitive information and later reproduce it without access to the original source, and that agentic self-modification removed a learned refusal behaviour; in both cases the change affected every service and coding agent powered by the shared model. No CVE. Relevance for organisations running open-weights agents with write access to model weights or redeploy pipelines: constrain agent tooling, separate training/redeploy privileges from task agents, and monitor unexpected fine-tune/redeploy actions. (source: Irregular) Correction (31 Oct 2026): removed the SecurityWeek link and credit, which this desk cannot read; every detail now comes from Irregular's post, and the wording on secrets now follows Irregular ('sensitive information'). The card date stays 16 September 2026, the post's date. (source: Irregular)
Irregular — Agentic Self-Modification in Open-Weights Systems (16 Sep 2026)
Micah Lee (16 September 2026; dataset from DDoSecrets / stegan0gram field extraction, also covered by 404 Media and Wired) analyses firmware from an in-use Flock Safety automatic licence-plate reader (ALPR) camera. The unit ran a modified Android 8.1 build dated 5 June 2025 on Linux 3.18.71 — far past vendor/Google support — and ships multiple Flock apps. Lee documents a hard-coded x-api-key in an app used to request device credentials from hpnotiq.flocksafety.com (MAC-address keyed), with returned credentials stored in plaintext and usable to mint bearer tokens via device-login.flocksafety.com. Lee lists older public Android/kernel CVEs the patch level likely predates but does not claim live exploitation tests on this hardware. Flock gave a statement to 404 Media/Wired (per Lee). No CVE assigned in the write-up. (source: Micah Lee analysis)
Micah Lee — Flock cameras hard-coded credentials (16 Sep 2026)
The CVE record (published 15 September 2026, 16:41 UTC; 16 September, 12:41 am Perth) covers CVE-2026-89026 in Issabel Framework (web UI for Issabel PBX / Asterisk). Before commit b97dbaf0b71c1c36f841e672b664afbeb02773bd the pbxapi index.php embeds a hard-coded HS256 JWT signing key identical on every install (CWE-321). Unauthenticated attackers forge bearer tokens and call /pbxapi/manager/originate with the System application parameter so Asterisk runs arbitrary OS commands as the Asterisk user. The CVE record rates it CVSS 4.0 9.3 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and CVSS 3.1 9.8. Patch (1 August 2026) replaces the hard-coded key with a key from /etc/issabel.conf. Shadowserver first observed exploitation on 9 September 2026; scale/actors not detailed. Apply the patched framework commit or later; rotate any JWT material that relied on the shared key. (sources: CVE record; The Hacker News) Correction (25 Oct 2026): the card date has moved from 15 to 16 September 2026, the Perth date of the CVE record's publication (15 September, 16:41 UTC; 16 September, 12:41 am Perth). (source: CVE.org)
CVE.org — CVE-2026-89026 record (Issabel Framework hard-coded JWT key; published 16 Sep 2026 Perth)
Cisco PSIRT advisory cisco-sa-ISE-ABP-VNSW7Tn5 (first published 16 September 2026 16:00 GMT) covers CVE-2026-76460, a maximum-severity authentication bypass in an API of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC), regardless of configuration. Insufficient authentication control on an API endpoint lets an unauthenticated remote attacker send a crafted request and bypass the web-based management interface to gain unauthorised device access; Cisco notes successful exploitation may yield root command execution and that on-box evidence can be removed afterward. Cisco CVSS 3.1 base 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H); CWE-648; Bug CSCww39530. No workarounds; temporary mitigation: infrastructure ACLs restricting management/control-plane traffic to the device. Fixed software: ISE/ISE-PIC 3.5 Patch 4, 3.4 Patch 7, 3.3 Patch 12, 3.2 Patch 11, 3.1 Patch 12. Cisco PSIRT is aware of active exploitation; CISA added CVE-2026-76460 to KEV on 16 September 2026 (same alert also added Acronis CVE-2026-87886). Same-day Cisco ISE/ISE-PIC criticals including CVE-2026-76423 are noted as related context, not separate cards — only 76460 has claimed in-the-wild use in the PSIRT advisory. Hunt ise-kong/access.log for suspicious usernames and correlate off-box network/firewall logs. (sources: Cisco PSIRT; BleepingComputer)
Forever Security (16 September 2026; also The Hacker News) documents BragJack: a research technique where a malicious Chromium extension with common page-modify and declarativeNetRequest permissions injects into the trusted origin the browser AI "body" listens to, then commands the built-in assistant. Affected demos: Gemini Live in Chrome (CVE-2026-0628, CVSS 8.8 per CISA score cited by researchers; fixed in Chrome 143.0.7499.192, Jan 2026), Microsoft Edge (CVE-2026-55945, CVSS 4.2; fixed in Edge 150.0.4078.48, 2 Jul 2026), Perplexity Comet, Opera Neon, and Claude in Chrome (latter three without CVE; vendor bounty acknowledgements claimed). Impacts vary by product (agent hijack, local file read, camera/mic on Chrome). Researcher demos only — not reported in the wild; requires the attacker's extension already installed. (sources: Forever Security; The Hacker News)
Forever Security — BragJack research (16 Sep 2026)
Mandiant AI Risk and Resilience Report 2026 (Google Cloud; reported by The Hacker News 16 September) case study: after compromising a SaaS provider, an attacker hijacked an active AI coding-assistant session on a developer workstation. The assistant recommended a poisoned external package; once accepted, the attacker used the session to install an infostealer via a poisoned PyPI package, harvest GitHub OAuth tokens, and deploy the self-propagating Shai-Hulud worm across about 100 internal repositories (secret theft and programmatic exfiltration). Defenders: treat AI assistant tool-install prompts as high-risk; constrain package installs; rotate GitHub tokens; audit recent repo automation. (source: Mandiant/Google Cloud report)
Mandiant AI Risk and Resilience Report 2026 (Google Cloud)
Premier Medical Group of the Hudson Valley P.C. published a Notice of Data Security Incident: after disruption of some IT systems, investigation found an unauthorized party accessed certain files on 14 June 2026; on 14 July 2026 PMG determined files may have included patient names, contact information, dates of birth, health insurance information, provider names, internal patient IDs, dates of service, medication information, and treatment/diagnostic information. Law enforcement notified; enhanced safeguards and staff training cited. The HHS breach portal lists Premier Medical Group of the Hudson Valley P.C. (NY, healthcare provider) with 282,075 individuals affected, submitted 21 August 2026, as a hacking/IT incident involving a network server. How the attack occurred not disclosed. (source: HHS OCR breach portal)
Premier Medical Group — Notice of Data Security Incident
WSO2 security advisory WSO2-2026-5328 / CVE-2026-5430 (published 3 May 2026; Critical): JWT authentication can be bypassed when a token is signed with an unsupported algorithm, allowing unauthorized access and potential administrative account takeover. Vendor CVSS 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H); single-tenant deployments adjusted to 9.8 (S:U). Affected: WSO2 API Manager 4.1.0–4.6.0; API Control Plane 4.5.0/4.6.0; Traffic Manager 4.5.0/4.6.0; Universal Gateway 4.5.0/4.6.0. The Hacker News (16 September 2026) cites watchTowr honeypot telemetry capturing forged admin JWTs on 13 September 2026 — active in-the-wild exploitation attempts. Support subscription holders: apply stated update levels (e.g. API Manager 4.6.0 UL 21, 4.5.0 UL 57, 4.4.0 UL 72, 4.3.0 UL 108, 4.2.0 UL 197, 4.1.0 UL 257; Control Plane/Traffic Manager/Universal Gateway levels on the advisory). Community: GitHub fixes carbon-apimgt PR 13752 and product-apim PR 14167, or migrate to an unaffected release. Credits: Hacktron Team. (sources: WSO2 WSO2-2026-5328; The Hacker News) UPDATE 24–25 Sep 2026: CISA added CVE-2026-5430 to KEV on 24 Sep 2026 (catalog 2026.09.24; FCEB due 27 Sep) alongside Adobe CVE-2026-71362. CISA’s KEV shortDescription labels the issue a path-traversal / unrestricted file-upload RCE; the authoritative WSO2-2026-5328 advisory text remains JWT authentication bypass via unsupported signing algorithm — Cyberstack keeps the vendor description. (source: The Hacker News)
eSentire Threat Response Unit blog (published 15 September 2026, 7:00 am US Eastern; 7:00 pm Perth) details GhostCode, a novel OAuth 2.0 device-authorization phishing kit that hijacks Microsoft 365 accounts after the victim completes legitimate MFA on Microsoft's real sign-in page. Observed chain: Salesforce contact-form lure posing as a procurement officer for BJ's Wholesale Club, sales follow-up, NDA pretext, then a WeTransfer link to a password-gated HTML lure using three evasion layers (junk padding, character-level HTML comment injection and an AES-256-GCM-encrypted redirect URL); a Cloudflare Turnstile gate filters scanners before the device-code page. Kit requests a user_code using the Microsoft Authentication Broker application ID, presents a polished fake document portal, and captures tokens once the victim approves the attacker's device. eSentire describes Primary Refresh Token capture and, in one intrusion, nine successful API calls with the stolen token across a 78-second period and three devices registered within 78 seconds, with rotating residential proxy IP addresses matching the victim's geolocation. Distinct from password-stealing kits; MFA does not stop the flow because the victim authenticates Microsoft directly. Defenders: restrict or block device-code grant where unused, alert on Authentication Broker device registrations, treat unexpected WeTransfer/NDA procurement mail as high-risk, review Entra ID sign-in and device logs. (source: eSentire TRU) Correction (26 Oct 2026): removed the Cyber Security News credit and link; every detail on this card is from eSentire's report, and the title no longer describes the 78-second window as an MFA bypass time. (source: eSentire)
eSentire TRU — GhostCode device-code phishing kit (15 Sep 2026)
