BoletimSec•August 28, 2026•🇵🇹Translated from Portuguese

TeamViewer Patches High-Severity Flaws Allowing Remote Command Execution and Unauthorized File Writes

TeamViewer has released patches for two high-severity vulnerabilities in its remote access products that could allow attackers to execute arbitrary commands and write files outside intended directories.

The most critical flaw, identified as CVE-2026-19042 and assigned a CVSS score of 8.8, affects TeamViewer Remote, Tensor, and ONE Full Client and Host components on Linux prior to version 15.81.5. Successful exploitation grants command execution with the privileges of the currently logged-in user. To deliver the malicious message, an attacker must already appear in the victim's contact list or obtain explicit permission to send messages from external users.

The second vulnerability, CVE-2026-16444 with a CVSS score of 7.5, results from insufficient validation of file paths. It impacts TeamViewer clients for Windows, macOS, and Linux before version 15.81.5. During an active remote session, files transferred or content sent via the virtual clipboard may contain path traversal sequences, enabling writes outside the expected directory and potential code execution under the affected user's permissions.

Older product lines, including editions supporting Windows 7 and Windows 8 as well as legacy TeamViewer 13 and TeamViewer 14 releases, also received specific security updates. The vendor strongly recommends upgrading to the most recent available version to mitigate the risks.

No evidence of active exploitation of either vulnerability had been observed at the time the security bulletins were published.

Related articles

Securitylab•Vulnerabilities & Exploits

Managing Bug Bounty Programs: Handling Report Overload, Duplicates, and AI-Generated Submissions

Launching a bug bounty program is only the beginning; the real challenge lies in managing the influx of reports, filtering duplicates and AI-generated noise, and ensuring vulnerabilities are actually fixed. Standoff Bug Bounty recommends starting with private programs limited to 30-50 researchers to build internal processes before scaling. Companies like Flavau developed custom DevSecOps consoles that cut report triage time by a factor of 10 by automating duplicate detection and assignee assignment. The platform introduced neural slop windows that limit submissions based on researcher quality history, addressing the surge in AI-generated invalid reports observed in spring 2026. Fixed response timelines, clear ownership roles, and prioritized remediation of critical issues help maintain program effectiveness. Google’s decision to pause its OSS VRP in October 2026 due to automated report floods highlights broader industry concerns, yet experts maintain that human-driven independent validation remains essential. Key success metrics include reduced risk from fixed high-severity issues, lower average payout costs, and improved cross-team communication between security and development.

Habr•Vulnerabilities & Exploits

Researcher Bypasses Safe Exam Browser Checks in Moodle Using MITM Proxy and Canonical Config Key Hash

A detailed technical write-up describes how a student bypassed the proprietary Safe Exam Browser requirement for Moodle quizzes by reverse-engineering the single-header authentication mechanism. The bypass relies on fetching the public SEB configuration XML from the open endpoint, computing a canonical SHA256 hash known as ConfigKey, and injecting the resulting X-SafeExamBrowser-ConfigKeyHash header via mitmproxy. Moodle caches a successful check inside the PHP session, allowing all subsequent requests to be made from a normal browser without further header manipulation. Two implementations were created: a headless Python client for full automation of quizzes and a transparent mitmproxy addon that lets a user continue interacting with the test manually. The author also handled edge cases such as crossword OCR with Tesseract, dynamic qubaid and sequencecheck values on retakes, and audio listening sections. The resulting scores reached 772 out of 780 points, placing the account 22nd out of 372 students. The full code, including configkey.py, mitm_addon.py and unit tests, has been published under CC BY-NC-SA 4.0.

Security NEXT•Vulnerabilities & Exploits

Oracle Releases 655 Security Patches in November 2026 Critical Update

Oracle has published its November 2026 Critical Security Patch Update, delivering a total of 655 patches that address vulnerabilities across a wide range of products. The update resolves 640 unique CVEs after accounting for duplicates and supplements the regular quarterly Critical Patch Update. Affected products include Oracle Database Server, Oracle Java SE, MySQL Server, Oracle WebLogic Server, Oracle E-Business Suite, and Oracle VM VirtualBox. Among the fixes, Oracle Hyperion accounts for the largest share with 267 patches, followed by Oracle Supply Chain with 74 and both Oracle Fusion Middleware and Oracle E-Business Suite with 71 each. Of the vulnerabilities patched, 311 carry a CVSSv3.1 base score of 7.0 or higher, including 62 rated 9.0 or above, while 303 can be exploited remotely.

Habr•Vulnerabilities & Exploits

DPoP Enforcement Failure Allows Bearer Token Bypass in redb.Identity OpenID Server

A vulnerability in redb.Identity allowed DPoP-bound access tokens to be accepted without proof-of-possession on the /connect/userinfo and management API endpoints. The flaw affected versions 1.0.1 through 4.6.1 when DPoP was enabled and was assigned GHSA-vmj2-8phj-mfxf with a CVSS 3.1 score of 7.4. External researcher Rathnadeepan reported the issue privately on 4 November, enabling a same-day confirmation and a fix released in 4.6.2 just one day later. Existing test suites, including over 2,000 green tests across three databases, failed to catch the problem because they only verified positive cases and never tested rejection of missing or invalid DPoP proofs. The root cause traced back to endpoints that only inspected the Bearer scheme and an earlier OpenIddict migration change that disabled cnf validation for jkt-bound tokens. The project published the advisory without waiting for a CVE and added negative test cases plus demo scenarios to prevent similar gaps in the future.