CVE-2026-91742 json
Confused deputy in PriceTracking in Google Chrome on on iOS prior to 153.0.8010.47 allowed a remote attacker leveraging social engineering…
published last mo. modified last mo. also EUVD-2026-79987
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
Confused deputy in PriceTracking in Google Chrome on on iOS prior to 153.0.8010.47 allowed a remote attacker leveraging social engineering to bypass system access restrictions into a privileged page via crafted network traffic. (Chromium security severity: Medium)
Patch / fix
- google chrome 153.0.8010.47
- chromium Debian 12 153.0.8010.52-1~deb12u1
- chromium Debian 13 153.0.8010.47-2~deb13u1
- chromium Debian 14 153.0.8010.47-1
debian advisories DEBIAN-CVE-2026-91742
- chromium openSUSE Leap 16.0 153.0.8010.52-bp160.1.1
- chromium openSUSE Tumbleweed 153.0.8010.47-1.1
opensuse advisories openSUSE-SU-2026:21921-1openSUSE-SU-2026:11812-1
Is CVE-2026-91742 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-441 Unintended Proxy or Intermediary
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/09/stable-channel-update-for-desktop_0541751186.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/513858387
permissions-required
Sources
- CVE List CVE-2026-91742
- NVD CVE-2026-91742
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.