BTC $69,918.28 -5.17%
ETH $1,983.98 -3.41%
BNB $644.84 -5.02%
XRP $1.01 -2.82%
SOL $80.08 -3.78%
TRX $0.3147 -0.72%
DOGE $0.0651 -3.28%
ADA $0.1714 -1.12%
BCH $221.20 -3.50%
LINK $9.92 -2.16%
HYPE $72.16 +0.04%
AAVE $112.50 -5.47%
SUI $0.7885 -3.87%
XLM $0.1450 -1.42%
ZEC $948.63 -4.12%
AAPL $356.31 +0.07%
AMZN $268.52 +0.80%
GOOGL $300.97 +1.88%
MSFT $521.35 -0.00%
META $626.32 -0.73%
NVDA $165.62 +2.73%
TSLA $399.77 +3.13%
SNDK $938.18 -2.91%
INTC $61.52 +0.65%
SPCX $141.19 +0.91%
MU $803.83 +0.87%
AMD $580.38 +2.17%
BTC $69,918.28 -5.17%
ETH $1,983.98 -3.41%
BNB $644.84 -5.02%
XRP $1.01 -2.82%
SOL $80.08 -3.78%
TRX $0.3147 -0.72%
DOGE $0.0651 -3.28%
ADA $0.1714 -1.12%
BCH $221.20 -3.50%
LINK $9.92 -2.16%
HYPE $72.16 +0.04%
AAVE $112.50 -5.47%
SUI $0.7885 -3.87%
XLM $0.1450 -1.42%
ZEC $948.63 -4.12%
AAPL $356.31 +0.07%
AMZN $268.52 +0.80%
GOOGL $300.97 +1.88%
MSFT $521.35 -0.00%
META $626.32 -0.73%
NVDA $165.62 +2.73%
TSLA $399.77 +3.13%
SNDK $938.18 -2.91%
INTC $61.52 +0.65%
SPCX $141.19 +0.91%
MU $803.83 +0.87%
AMD $580.38 +2.17%

update

All
Article
Flash

Google urgently releases Chrome security update: fixes zero-day vulnerability already being exploited in the wild, urges users to upgrade immediately

On November 9, 2026, Google released an emergency stable channel update for the desktop Chrome browser, fixing nine security vulnerabilities, including a zero-day vulnerability that was already being exploited in the wild. This update raises the Chrome version on Windows and Mac platforms to 157.8103.5/.51, and to 157.8103.5 on the Linux platform, and will be gradually rolled out over the next few days to weeks. The core focus of this update is the high-risk vulnerability numbered CVE-2026-125350, which is a use-after-free issue in an XML component. Google explicitly stated in the announcement that "CVE-2026-125350 is known to be exploited in the wild," but did not disclose specific attack methods, the scale of victims, or attribution of the attack activities.The vulnerability was reported by an anonymous researcher on November 6, 2026, just three days before Google released the fix. Among the nine fixes, seven are classified as "high risk" and two as "medium risk." In addition to CVE-2026-125350, another high-risk vulnerability, CVE-2026-125346, also pertains to a use-after-free issue in an XML component, reported by Arni Hardarson of Neonix Security on October 12, 2026, but Google only marked CVE-2026-125350 as an actively exploited vulnerability. The other high-risk vulnerabilities include uninitialized resources in WebGL, improper FileSystem authorization, synthesizer buffer overflow, GPU out-of-bounds write, and V8 type confusion, most of which were discovered by Google's internal security team.Google also confirmed that the Android version of Chrome (157.8103.5) released on the same day includes the same security fixes as the desktop version, with no exceptions noted. Users on the Extended Stable channel should install the update released separately on November 9, with Windows and Mac versions being 156.8078.96, which also lists CVE-2026-125350 as a high-risk fix. The Hong Kong Government Computer Security Incident Coordination Centre (GovCERT.HK) issued a security alert on the same day, defining affected systems as versions prior to Chrome 157.8103.5, and pointed out that successful exploitation of the related vulnerabilities could lead to remote code execution, denial of service, tampering, or bypassing security restrictions. The Hong Kong Computer Security Incident Coordination Centre (HKCERT) rated the risk level of this update as "extremely high risk." Google explained in the announcement that access to vulnerability details and links may remain restricted until most users complete the update. The company recommends that users manually check and trigger the update via "Settings → About Chrome," and restart the browser after completing the update for the patch to take effect. For users still running versions prior to Chrome 157.8103.5, the current priority action is to confirm the version number and restart immediately to complete the upgrade.

first_img SEC Updates Token Classification FAQ: Adapting to DUNA Entities, Clarifying Issues of Functionality and Decentralization Boundaries, etc

a16z Chief Legal Counsel Miles Jennings posted on X that the U.S. Securities and Exchange Commission (SEC) has released new FAQs that further clarify its token classification framework. He pointed out that Question 1.4 clearly states that systems can maintain decentralized governance and use legal entities such as DUNA; Question 1.5 distinguishes between licensed and unlicensed systems; and Question 1.6 clarifies the difference between "functional" and "decentralized."The SEC's Division of Corporation Finance updated the relevant Q&A on November 2. The response to Question 1.4 states that participants in a widely governed functional crypto system, if not interconnected and without formal or informal collaborative arrangements other than participating in that governance system, typically do not constitute a group of persons or entities defined as "centralized parties"; even if they do form such a group, they must still possess operational, economic, or voting control to meet the definition of "centralized parties." This conclusion also applies to cases where the governance system belongs to an organization, association, or foundation, and participation is based on holding native crypto assets.The response to Question 1.5 states that centralized party oversight of participants refers to the authority to control access to the system at the protocol, validator, or user level, such as unilaterally granting or restricting access, deciding on upgrade voting procedures, controlling who can participate in consensus, or modifying rule code, revoking transactions, and access. The response to Question 1.6 states that "functional" refers to native crypto assets being usable according to the system's programmed purposes, while "decentralized" refers to the system operating autonomously without any person, entity, or group having operational, economic, or voting control; the two are distinct concepts. The above responses represent the views of the staff of the Division of Corporation Finance and do not constitute SEC rules or statements.

OnKey founder: The iPhone 11 and earlier models have hardware vulnerabilities that cannot be fixed through system updates, and it is not recommended to use them for storing mnemonic phrases

OnKey founder Yishi posted on platform X to remind users that using older iPhone models as cold wallets for cryptocurrency assets may pose security risks. The checkm8 vulnerability exists in the BootROM of iPhone 4S to iPhone X, and the usbliter8 vulnerability, which was disclosed in June this year, affects iPhone XS, XR, 11 series, and second-generation SE, all involving the device's low-level boot code, which cannot be fixed through iOS system updates. Once an attacker gains physical access to the device, they can execute code via the USB interface before iOS boots, and turning on airplane mode cannot prevent such attacks.Yishi advises that iPhone 11 and earlier models are not recommended for storing mnemonic phrases. Users who have used such devices to save mnemonic phrases should generate a brand new mnemonic phrase in a trusted environment and migrate their assets, rather than just changing the wallet address under the original mnemonic phrase. Additionally, users should promptly update their systems, use more complex device and wallet passwords, avoid charging through public USB interfaces, and be vigilant about potential physical attacks during periods when the device is out of their control for extended periods.Previously, OneKey founder Yishi had posted on platform X suggesting users use iPhones as cold wallets, but only recommended using iPhone 17 or newer models.
app_icon
ChainCatcher Building the Web3 world with innovations.