Update the V8 Javascript engine to version 1.1.10.14 to fix issues with regular expressions.

Update Gears to the latest release, 0.5.25.0.

In addition, this release fixes the following security issues:

CVE-2009-2555 Heap overflow with Javascript regular expressions

Evaluating a specially-crafted regular expression in Javascript on a web page can lead to memory corruption and possibly a heap overflow. Visiting a maliciously crafted website may lead to a renderer (tab) crash or arbitrary code execution in the Google Chrome sandbox.

Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.

Credit: This issue was found by the Google Chrome security team.

Mitigations:

A victim would need to visit a page under an attacker's control.

Any code that an attacker might be able to run inside the renderer process would be inside the sandbox. Click here for more details about sandboxing.

CVE-2009-2556 Memory corruption in the browser process

A compromised renderer (tab) process could cause the browser process to allocate very large memory buffers. This error could cause the browser process (and all tabs) to crash or possibly allow arbitrary code execution with the privileges of the logged on user. To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process.

Severity: Critical. In conjunction with a vulnerability allowing arbitrary code to run in the renderer, an attacker might be able to run code with the privileges of the logged on user.

Credit: This issue was found by the Google Chrome security team.

Mitigations:

A victim would need to visit a page under an attacker's control.

The attacker must exploit a second vulnerability to control the renderer process.

This build seems to having some problems in relation to facebook websites. The login process are slow and error arises. When attempt to click the back button, the process is terminate without loading the content of the websites. When click the reload button, the process is on-going without stopping and hard to login and open up the homepage of an account. As a result, error messages keep on appearing without any other reason. Previous build seems to running stable and error free. Please fix this issue as soon as possible.

I have problems relating to HTTP POSTs and it may be relating to Jeffrey's problems.

It seems occasionally when a Chrome rendering process starts up, the process will refuse to send POST data along with HTTP POSTs, breaking many websites. This persists for the lifetime of the process and it must be killed and restarted to fix HTTP POST requests.

It is most notable on web forums where POSTs are used for logging in and making... well, posts.

Using Gmail with Chrom leads to privacy violation issue: when the Gmail session is started through a http url (instead of https), snippets of the email conversations are shown in the Chrome history search.

This can be quite serious depending on what information is displayed and on who reads it.

This build seems to be unstable when click on the back button whereby the error message occur frequently and causing people desire to switch to the latest Google Chrome development build version 3.0.193.1. Besides that, the latest development have a tiny problem related to the facebook webpage whereby the chat session cannot click and show a list of people who is available for chat. Please fix this bug as soon as possible before anything happen.