Afina Core Update to Chromium 157.0.8103.79
Afina has moved to browser core 157.0.8103.79, which includes 83 security fixes: 5 critical and 78 high-severity issues. The update covers components that process web pages, execute JavaScript, render graphics, and control access to resources.
Profiles, accounts, and automations interact with website content every day. The state of the browser core therefore has a practical impact on long-running work sessions in Afina.
What changed in core 157.0.8103.79
Google included 83 security fixes in the corresponding Chrome release. CVE identifiers, affected components, and the people who reported the issues are listed in the official bulletin.
Five critical vulnerabilities belong to the use-after-free class. This error occurs when a program continues to access an area of memory after it has been released. It can cause memory corruption and crashes. Under certain conditions, it may also create an opportunity to execute malicious code, although the specific outcome depends on the vulnerability and how it is exploited.
Which critical vulnerabilities were fixed
The critical fixes cover five browser-core components. Each one handles a separate part of web-content processing.
| Vulnerability | Component and purpose | Reported by |
|---|---|---|
| CVE-2026-126885 | ServiceWorker, background website tasks, caching, and offline operation | Xinyang Ge |
| CVE-2026-126895 | CSS, processing styles and page presentation | Xinyang Ge |
| CVE-2026-126879 | Layout, calculating element sizes and positions | Xinyang Ge |
| CVE-2026-126846 | Skia, rendering graphics, text, and other elements | |
| CVE-2026-126911 | Accessibility, support for assistive technologies including screen readers | Andrew Boni |
Other fixes address errors in V8, which executes JavaScript, the ANGLE and Skia graphics components, and resource-access checks. CVE-2026-126864 in V8 was reported by Jihyeon Jeong, while CVE-2026-126916 was reported by OpenAI Codex Security (kylebot). The package covers memory-handling errors, type confusion, information leaks, and incorrect permission checks.
Why the update matters for work in Afina
Profile isolation and digital-fingerprint settings perform their own functions. The core update works at another level by fixing errors that occur while processing web pages and executing their code.
This is especially relevant when working with multiple accounts or running long automation scenarios. Before moving to the new version, finish active tasks, save your results, and schedule a short pause for the update and version check.
How to update Afina and verify the core version
The browser core updates automatically when you sign in to the Afina app. You do not need to start a separate update for it.
To check the application and core versions:
- finish active tasks and save your work
- open “Settings” → “Main”
- find the “App version” field
- click “Check for updates” and follow the Afina prompts
- check the “Browser version” field below
- confirm that it displays 157.0.8103.79
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 157.0.8103.79. You can verify the number in the “Browser version” field under General settings.
How many security fixes does the update contain?
The release contains 83 fixes: 5 critical and 78 high-severity issues.
What does use-after-free mean?
It is an error in which a program accesses memory after it has been released. It may cause memory corruption or a crash, while the specific consequences depend on the exploitation conditions.
Which components received critical fixes?
The critical fixes cover ServiceWorker, CSS, Layout, Skia, and Accessibility.
Do I need to update the browser core separately?
No. The core updates automatically when you sign in to the Afina app.
Where can I check the browser version in Afina?
Open “Settings” → “General” and find the “Browser version” field below the application version.
