Disclosed Chromium Security Bugs

Potential type confusion in wasm and js interaction

#379009132•Reporter: li...@gmail.com
$8,000
2/26/2025

DCHECK failure in 0 <= prev_pc_offset && prev_pc_offset <= code->instruction_size() in code-stats.

#373025978•Reporter: 24...@project.gserviceaccount.com
$0
2/26/2025

V8 sandbox violation in v8::internal::TranslatedValue::kind

#376496315•Reporter: 24...@project.gserviceaccount.com
$0
2/26/2025

v8_wasm_compile_fuzzer: Crash in Builtins_JSToWasmWrapperAsm

#378701682•Reporter: cl...@chromium.org
$0
2/25/2025

Crash in Builtins_JSEntryTrampoline

#379159146•Reporter: sa...@google.com
$0
2/25/2025

CHECK failure: constant.has_value()

#379159143•Reporter: 24...@project.gserviceaccount.com
$0
2/25/2025

MSL threadgroup allocations can be coerced to be too small

#378725734•Reporter: jr...@google.com
$0
2/25/2025

A vulnerability in Chrome mobile allows attackers to trigger fido:/ links, hijacking FIDO2 accounts by tricking victims into authenticating malicious requests, bypassing 2FA, and taking over accounts.

#370482421•Reporter: sp...@protonmail.com
$6,000
2/24/2025

shaderc:shaderc_fdp_fuzzer: Container-overflow in glslang::HlslParseContext::decomposeIntrinsic

#380569852•Reporter: 87...@developer.gserviceaccount.com
$0
2/24/2025

rdkit:mol_data_stream_to_mol_fuzzer: Use-of-uninitialized-value in void RDKit::ParseV3000AtomProps

#380569842•Reporter: 87...@developer.gserviceaccount.com
$0
2/24/2025
Showing 5011-5020 of 13102 bugs
1...501502503...1311