SUSE · chromedriver-157.0.8103.38-1.1 on GA media
Affects SUSESource GCVE Database
Not known to be exploited : upgrade SUSE to 157.0.8103.38 when convenient.
Data as of 6 Nov 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 157.0.8103.38
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Chrome to 157.0.8103.38.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Upgrade to the chromedriver-157.0.8103.38-1.1 package on openSUSE Tumbleweed GA media to apply the security fixes. No additional mitigation guidance is available due to lack of detailed advisory content.
Description
Multiple security issues have been fixed in the chromedriver-157.0.8103.38-1.1 package on the GA media of openSUSE Tumbleweed. The package update addresses a range of vulnerabilities identified by numerous CVE identifiers. No specific details on the nature or impact of these vulnerabilities are provided.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_12426-1.json (opens in a new tab)
- suse.com/security/cve/CVE-2026-121029/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121030/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121031/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121032/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121033/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121034/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121035/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121036/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121037/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121038/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121039/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121040/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121041/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121042/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121043/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121044/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121045/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-121046/ (opens in a new tab)