Official Afina Core Update to Chromium 158.0.8127.37

Afina has moved to browser core 158.0.8127.37, making it one of the first antidetect browsers on Chromium 158. The update is already available on Windows and macOS at the same time.
Google promoted Chrome 158 to the stable channel on November 17, 2026, and is rolling it out to regular users gradually. Afina profiles now run on the same core generation as the latest stable Chrome release.
What's new in the Chromium 158 core and web standards
The Chrome 158 release contains 204 security fixes: 6 critical, 62 high, 82 medium and 54 low severity. CVE identifiers and reporters are listed in the official bulletin.
| Vulnerability | Component and purpose | Reported by |
|---|---|---|
| CVE-2026-130963 | WebView, embedding web content into applications | |
| CVE-2026-131031 | GPU, hardware-accelerated graphics | Xinyang Ge (Anthropic) |
| CVE-2026-131060 | Media, audio and video playback | Xinyang Ge (Anthropic) |
| CVE-2026-131008 | GarbageCollection, freeing unused memory | Xinyang Ge |
| CVE-2026-130975 | WebAudio, processing and generating sound | Xinyang Ge (Anthropic) |
| CVE-2026-131054 | ANGLE, translating WebGL calls to system graphics APIs |
Three of the critical fixes are use-after-free errors, when a program accesses memory after it has been released. The other three are out-of-bounds writes and a buffer overflow.
Chromium 158 also enables new web platform features by default:
- Web Install API and the
<install>element: a website can prompt the user to install a web app by its manifest URL - Media element pseudo-classes
:playing,:paused,:buffering,:mutedand others for styling audio and video by state - WebTransport improvements: the
drainingsignal, reliability attributes and a hint for the expected number of incoming streams ::highlight(*)universal selector for custom text highlightsfocus-without-user-activationpermissions policy: the embedding page controls whether content in an iframe can move focus programmatically
Why the update matters for work and fingerprints in Afina
A website sees not only the browser version in the User-Agent and Client Hints, but also which APIs, CSS properties and rendering behavior the engine actually supports. When the declared version and the real feature set match, the profile looks like regular Chrome 158 rather than an outdated build with a substituted version string.
This brings three practical benefits for multi-account work:
- Matching current traffic. Profiles run on the same core generation as most up-to-date Chrome users, without a lag of one or two releases
- Account protection. The fixes close vulnerabilities in GPU, ANGLE, WebAudio and Media, the components that process graphics, audio and video on web pages
- Stable sessions. Long automation scenarios run on a core with current fixes for memory errors that can cause crashes
The core update does not replace correct profile settings: the result on a specific website still depends on the proxy, fingerprint configuration and account activity. Antifraud systems weigh many signals, so no browser can guarantee the absence of checks.
How to check the core version in Afina settings
The browser core updates automatically when you sign in to the Afina app. You do not need to start a separate update.
To check the core version:
- finish active tasks and save your work
- open Menu → "Settings" → "Main"
- find the "App version" field and click "Check for updates" if Afina offers a new build
- check the "Browser version" field below
- confirm that it displays 158.0.8127.37
If you need assistance, visit the official Afina website and use the current support channels.
DownloadFAQ — Frequently Asked Questions
Which browser-core version does Afina now use?
Afina has moved to core version 158.0.8127.37 (Chromium 158). You can verify the number in the "Browser version" field under Main settings.
Is the update available on Windows and macOS?
Yes. Chromium 158 was released in Afina for Windows and macOS at the same time.
How many security fixes does Chromium 158 contain?
The release contains 204 fixes: 6 critical, 62 high, 82 medium and 54 low severity.
Why does the core version matter for fingerprints?
Websites compare the declared browser version with the APIs and behavior the engine really supports. A current core removes the mismatch between the version string and the actual feature set.
Do I need to update the browser core separately?
No. The core updates automatically when you sign in to the Afina app.
