BTC $68,762.42 -6.66%
ETH $1,926.03 -6.09%
BNB $633.61 -6.45%
XRP $1.00 -3.62%
SOL $78.56 -5.44%
TRX $0.3109 -1.96%
DOGE $0.0634 -5.52%
ADA $0.1678 -2.94%
BCH $216.62 -5.68%
LINK $9.69 -4.02%
HYPE $70.81 -1.95%
AAVE $110.32 -6.92%
SUI $0.7709 -5.79%
XLM $0.1419 -3.14%
ZEC $916.91 -6.74%
AAPL $357.16 +0.31%
AMZN $268.19 +0.72%
GOOGL $300.05 +1.56%
MSFT $521.07 -0.05%
META $625.20 -0.56%
NVDA $163.41 +1.31%
TSLA $398.07 +2.62%
SNDK $918.02 -4.13%
INTC $60.75 -0.05%
SPCX $140.22 +0.30%
MU $790.21 -0.16%
AMD $573.04 +1.72%
BTC $68,762.42 -6.66%
ETH $1,926.03 -6.09%
BNB $633.61 -6.45%
XRP $1.00 -3.62%
SOL $78.56 -5.44%
TRX $0.3109 -1.96%
DOGE $0.0634 -5.52%
ADA $0.1678 -2.94%
BCH $216.62 -5.68%
LINK $9.69 -4.02%
HYPE $70.81 -1.95%
AAVE $110.32 -6.92%
SUI $0.7709 -5.79%
XLM $0.1419 -3.14%
ZEC $916.91 -6.74%
AAPL $357.16 +0.31%
AMZN $268.19 +0.72%
GOOGL $300.05 +1.56%
MSFT $521.07 -0.05%
META $625.20 -0.56%
NVDA $163.41 +1.31%
TSLA $398.07 +2.62%
SNDK $918.02 -4.13%
INTC $60.75 -0.05%
SPCX $140.22 +0.30%
MU $790.21 -0.16%
AMD $573.04 +1.72%

zero

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.

Anthropic applies zero-knowledge proof technology to AI reasoning to prevent model swapping

Anthropic has open-sourced FlashProve, bringing the commonly used zkSNARK (zero-knowledge proof) technology from the cryptocurrency field into AI model inference.This technology was originally designed to prove the validity of blockchain transactions without disclosing transaction details. Anthropic aims to use it to solve another problem: when users pay a high price for an AI model's API, how can they know if the service provider has secretly switched to a cheaper model?FlashProve allows service providers to first generate encrypted fingerprints for the model weights and then provide mathematical proof for the inference results. Users do not need to obtain the model weights or rerun the model; they can check whether the specified output comes from the previously committed set of weights. Claude was also involved in the development and optimization of this system.Anthropic has already completed experiments on Meta's 400 billion parameter model Llama 4 Maverick. For every 1024 tokens of context processed, the generated proof is about 19 MB, and verification on a regular CPU takes about 17 seconds.However, currently, each proof can only verify one output token and cannot validate an entire response. The GPU computation time required to generate the proof is also about 70 to 95 times that of regular inference. Whether it can be used to identify API service providers that secretly switch models in the future will depend on when the cost of proof generation can be reduced.

XRP Ledger developers test a zero-balance account creation plan, which is proposed to be funded by the sponsor to cover the 1 XRP reserve requirement

According to CoinDesk, XRP Ledger developers are testing a new feature that aims to allow the creation of blockchain accounts with an initial balance of zero, with existing accounts bearing the reserve required for new accounts, thereby lowering the financial threshold for payment applications and automated software to create wallets on a large scale. This proposal was submitted on October 15 in the form of a SponsoredAccountCreate transaction proposal.According to current XRP Ledger rules, each account must reserve at least 1 XRP as a reserve, meaning that creating 100,000 independent accounts would require locking up 100,000 XRP. The new proposal intends for sponsored accounts to bear this reserve requirement, and a broader fee sponsorship mechanism in the future could also allow applications to pay transaction fees on behalf of users, but the overall reserve requirement for the network will not be eliminated. This feature is expected to lower the usage threshold for scenarios such as embedded wallets, RLUSD stablecoin payments, and AI agent automated payments.However, the related code is still under review, and the sponsorship mechanism it relies on has not yet gone live on the mainnet. As of October 19, the mechanism has only received 11 votes out of the 35 required validator votes, still falling short of the 29 votes needed for approval.
app_icon
ChainCatcher Building the Web3 world with innovations.