#BrowserSecurity
Edge exploit uses logic flaws, one-click-less UXSS, and read:// hacking to break out of its sandbox. #Edge #BrowserSecurity #ZeroClick #UXSS #Cybersecurity #WindowsIntegrations thedailytechfeed.com/new-zero-cli...
October 29, 2026 at 9:54 AM
319 Chrome extensions hijack searches via search_provider overrides—millions affected, privacy exposed. #Privacy #BrowserSecurity #ChromeExtensions #SearchHijacking #Cybersecurity #ThreatIntel thedailytechfeed.com/319-chrome-e...
October 29, 2026 at 9:53 AM
Orange Tsai and DEVCORE won Pwn2Own Berlin with a full Microsoft Edge exploit chain made of logic bugs alone - no memory corruption, no AI involved. $175,000 and a Pwnie award. https://blog.orange.tw/posts/2026-10-the-last-proof-of-human-craft-browser-full-chain/

#BrowserSecurity
October 29, 2026 at 9:52 AM
October 29, 2026 at 7:35 PM
October 28, 2026 at 11:08 AM
📣 New Podcast! "ChatGPT Security Flaw: How a Shared Link Could Expose Private Conversations and Execute Malicious Code" on @Spreaker #aitsecurity #artificialintelligence #browsersecurity #bugbounty #chatgptsecurity #chatgptvulnerability #codeexecution #cybersecurity #cyberthreats #dataprivacy
ChatGPT Security Flaw: How a Shared Link Could Expose Private Conversations and Execute Malicious Code
https://www.osintinvestigate.com A simple ChatGPT shared link could become a serious cybersecurity threat. Security researchers from Parameter discovered a vulnerability that allowed attackers to execute malicious code within a logged-in ChatGPT session and potentially access private conversations. In this episode, we explore how the attack worked, how a browser sandbox was bypassed, why MathLive and insecure message handling played a crucial role, and how OpenAI responded with a security fix. Discover the implications for AI security, data privacy, and the protection of sensitive information in the age of generative artificial intelligence. The vulnerability was reported through OpenAI's bug bounty program, classified as P1, and patched on October 26, 2026. No real-world exploitation was reported by the researchers. Find out why this discovery highlights the importance of secure AI architectures and responsible vulnerability disclosure.
www.spreaker.com
October 31, 2026 at 4:00 PM
社内のパソコンでChromeを使っていると「うちはセキュリティ更新が済んでるのか?」と聞かれ、全台把握できていないことがあります。この記事では、[Google Chrome について]で版と再起動の表示を確認し、PCごと・日付付きの点検表に記入する手順を紹介。架空のサンプル商店の記入例、再起動待ちの人への連絡文、管理者への問い合わせメモもあります。https://tips.jp/u/ai-lab/a/chrome-156-update-check
#Chrome #GoogleChrome #ChromeUpdate #BrowserSecurity #総務
Chrome 156のセキュリティ修正21件|社内PCの版と再起動待ちを点検する確認表と連絡文 | Tips
2026年10月29日付のChrome公式投稿(156.0.8078.79/.80、修正21件・Critical1件)を整理。Googleヘルプの手順で社内PCの版と再起動待ちを確認し、点検表と再起動をお願いする連絡文を作る方法をまとめます。コードや設定変更は不要で、確認日つきで記録できます。
tips.jp
October 30, 2026 at 10:33 PM
ChatGPT’s Chrome extension can now analyze all open tabs and manage browser tasks—big power, big responsibility. #AI #BrowserSecurity #ChatGPT #BrowserSecurity #AI #Privacy #ChromeExtension #OpenAI https://thedailytechfeed.com/chatgpt-chrome-extension-now-reads-analyzes-all-open-tabs/
October 21, 2026 at 7:54 AM
Chrome uses Gemini AI to flag update scams & ClickFix attacks—better warnings, broader protection. #Chrome #GeminiAI #Security #BrowserSecurity #ClickFix #SafeBrowsing thedailytechfeed.com/chromes-gemi...
October 21, 2026 at 3:25 PM
October 21, 2026 at 2:23 PM
eMudhra CA key breach forces browser and root store fixes — urgent patches needed. #Security #CertificateAuthority #TLS #eMudhra #BrowserSecurity #Vulnerability thedailytechfeed.com/eight-emudhr...
October 20, 2026 at 5:25 PM
Browsers Revoke Trust in Eight eMudhra Certificates After Private Key Compromise #Browser #BrowserSecurity #CertificateAuthority
Browsers Revoke Trust in Eight eMudhra Certificates After Private Key Compromise
 Major browser vendors and certificate trust stores have blacklisted eight intermediate certificates issued by Indian certificate authority eMudhra following the discovery of recoverable private keys. The compromised keys could have been used to create fraudulent HTTPS certificates and impersonate secure websites on affected systems.  The affected certificates were issued in April 2025, and blocked in Firefox and Chrome on October 17 by Mozilla and Google, followed by Apple on October 19 and Microsoft on October 20. Sectigo took revocation action, and Cloudflare updated its services in response.  Google stated the keys had been generated with insufficient entropy, allowing an attacker to reconstruct them and use them to create fraudulent, but otherwise valid, certificates. Although eMudhra has revoked the certificates in question and informed downstream trust stores, some systems may require software updates before ceasing to trust the compromised certificate authorities.   Mozilla’s Dennis Jackson has published a tool to help users check whether their systems trust the affected certificates, warning that “reconstructing the private keys [was] actually kind of easy” due to a severe flaw in the certificate creation process.  Jackson revealed that, aside from the final byte, all the keys were zero, and therefore could be reconstructed almost instantly using the baby-step giant-step algorithm to solve the discrete logarithm problem. He added that several people had independently managed to recover the keys.  Certificate Transparency logs have revealed no evidence of abuse of the compromised keys, but this cannot guarantee that they were not used to compromise HTTPS sites, as not all clients enforce Certificate Transparency policies. Anyone whose systems trust the compromised certificates could be at risk, as the keys could have been used to impersonate secure websites without detection.   eMudhra stated that the error was caused by a script used in the key generation ceremony which resulted in a second, weaker key pair being created. This was used to generate certificate signing requests because the labels on the keys were similar enough to mislead the process.  The company stated that the certificates in question were created for export to its data centres in the United States and Europe to satisfy data sovereignty requirements, and were not in production use, with the exception of one.   eMudhra identified human errors at several points during the process, but stated that it was investigating potential coding issues and process weaknesses, including maker-checker controls, which are meant to prevent errors by ensuring that no single individual has control over any critical process. eMudhra has undertaken to recheck all key generation ceremonies it has performed during the coming week.  The incident demonstrates the critical importance of key generation security, internal controls and certificate revocation, and the need for organisations to update their software and trust stores following a security incident to prevent further compromises.
dlvr.it
October 22, 2026 at 5:34 PM
October 17, 2026 at 6:31 AM
October 16, 2026 at 1:06 PM