ChromeWeb browser · Google

CVE-2025-1921

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-05

Fix available

A fix is available. Upgrade to 134.0.6998.35 or later.

See remediation →

72/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Inappropriate implementation in Media Stream in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to obtain information about a peripheral via a crafted HTML page. (Chromium security severity: Medium)

Technical summary

dbcve analysis · high confidence

This is an information disclosure vulnerability in Google Chrome's Media Stream API. A remote attacker can craft a malicious HTML page to obtain information about connected peripherals (such as cameras, microphones) without proper authorization or isolation. The vulnerability stems from inappropriate implementation in how the browser handles media stream permissions and device enumeration.

MitigationUpdate Google Chrome to version 134.0.6998.35 or later. For enterprise environments, deploy the update via standard software distribution mechanisms and verify the installed version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 134.0.6998.35

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed Google Chrome version

Navigate to chrome://settings/help or enter chrome://version in the address bar to view the installed version number

Affected if The installed version is lower than 134.0.6998.35 (e.g., 134.0.6998.34 or earlier)
Verify Chrome is the affected browser

Confirm the browser is Google Chrome and not a Chromium-based alternative (such as Edge, Brave, or Opera)

Affected if The browser is Google Chrome and the version is below 134.0.6998.35
Confirm Media Stream API is accessible

Open a webpage and attempt to access navigator.mediaDevices.enumerateDevices() via browser developer console (F12) - this API must be available for the vulnerability to be exploitable

Affected if The enumerateDevices() method returns device information without prompting for permission or returning errors
Check for existing permission prompts

Visit a website that requests camera/microphone access and observe whether the permission prompt appears correctly

Affected if Websites can enumerate connected devices without triggering the expected permission prompt, indicating the vulnerability is present

A user is affected if running Google Chrome version below 134.0.6998.35 and the Media Stream API permits device enumeration without proper authorization prompts.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 134.0.6998.35 or later

Fixed in 134.0.6998.35

Interim mitigation

Update Google Chrome to version 134.0.6998.35 or later. For enterprise environments, deploy the update via standard software distribution mechanisms and verify the installed version.

Recommended fix High confidence

Chrome version 134.0.6998.35 or later

Open Google Chrome application
Navigate to Settings > Help > About Google Chrome (or go to chrome://settings/help in the address bar)
Chrome will automatically check for updates
If update 134.0.6998.35 or later is available, click 'Update Google Chrome'
Wait for the download and installation to complete
Restart Google Chrome to apply the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing1.0 h

4.0 hours of engineering $750

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-1921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

chromereleases.googleblog.comRelease Notes
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1921 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-1921?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 134.0.6998.35 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-1921 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References