Nginx Leaves Dynamic Tables Unused in HTTP/2 and HTTP/3 Responses
Nginx applies header compression asymmetrically in both HTTP/2 and HTTP/3. While clients compress repeated headers after the first transmission, the server always emits full literals, keeping response header sizes constant regardless of repetition count.
Measurements on a minimal stand with four identical requests show server responses locked at 131 bytes under HTTP/3 and 129 bytes under HTTP/2. Client requests, by contrast, drop from 246 bytes to 8 bytes once the dynamic table is populated.
Inspection of release-1.31.3 reveals the root cause inside ngx_http_v3_filter_module.c: all twenty-two invocations of ngx_http_v3_encode_field_ri and ngx_http_v3_encode_field_lri pass a zero value for the dynamic flag, forcing every field to be encoded as a literal. The field-section prefix is likewise emitted with insert_count and delta_base set to zero. No server-side encoder stream of type 0x02 is ever opened.
The identical limitation exists in the HPACK implementation. The HTTP/2 filter module contains zero references to ngx_http_v2_hpack_t and explicitly sends a Dynamic Table Size Update of zero on the first HEADERS frame, disabling client-side table usage for server responses.
The receiving path, however, is fully functional. ngx_http_v3_table.c implements insertion, eviction, blocked-stream tracking and the default 4096-byte table capacity announced in the SETTINGS frame. Debug logs confirm that client-supplied headers are correctly inserted and later referenced by index.
The asymmetry is explicitly allowed by RFC 9204 §4.2, yet it eliminates the compression gains that motivated the introduction of QPACK and HPACK. The unused encoder code path also contributed to a use-after-free vulnerability (CVSS 9.2) in the QPACK decoder earlier this year.
Related articles
JetBrains TeamCity CVE-2026-63077 Actively Exploited in the Wild, JPCERT Urges Immediate Patching and Breach Investigation
A critical deserialization vulnerability tracked as CVE-2026-63077 has been discovered in JetBrains TeamCity, allowing unauthenticated remote code execution through the agent polling protocol. The flaw was privately reported to JetBrains on July 10, 2026, and publicly disclosed on July 27 with patches released in TeamCity 2026.1.3 and 2025.11.7. Following disclosure, active exploitation was confirmed, prompting CISA to add the vulnerability to its Known Exploited Vulnerabilities Catalog on August 5 and mandate federal agencies to remediate by August 8. JetBrains issued its own exploitation warning on August 7. JPCERT/CC has verified that affected versions remain in use within Japan and notes that public exploit code is now available, recommending organizations verify their deployments, apply updates promptly, and conduct compromise assessments.
Attackers Actively Exploit Critical SharePoint Authentication Bypass CVE-2026-55040 After Public PoC Release
Active exploitation of CVE-2026-55040, a critical authentication bypass vulnerability in Microsoft SharePoint Server, has intensified following the public release of a proof-of-concept exploit. The flaw, which carries a CVSS score of 9.1, stems from multiple defects in the JWT token validation pipeline and allows remote attackers to impersonate any user, including administrators, without valid credentials. Affected versions include SharePoint Server Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016, with heightened risk for instances exposed to the internet. Microsoft released patches in July 2026, and organizations are urged to apply them immediately while restricting external access and monitoring IIS logs for anomalous administrative activity. The vulnerability has already been chained with other flaws in real-world incidents involving persistence, data theft, and credential rotation responses.
Microsoft Patches High-Severity Outlook Flaw Allowing Remote Code Execution
Microsoft has addressed a high-severity vulnerability in Outlook tracked as CVE-2026-70329 with a CVSS score of 8.8. The flaw stems from an integer overflow during data processing that can trigger memory corruption and alter the application's execution flow. Exploitation occurs over the network without requiring authentication or privileges, though some user interaction is necessary to process the malicious content. Successful attacks grant code execution under the privileges of the logged-in user, potentially enabling malware installation, file access, data theft, or lateral movement. The issue impacts Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021, Office LTSC 2024, and Outlook 2016 on both 32-bit and 64-bit systems. A dedicated patch KB5002755 updates Outlook 2016 to build 16.0.5565.1000, while Click-to-Run versions receive fixes through standard Microsoft update channels.
Malicious SIM Card Commands Hijack EV Chargers and IoT Modules via Legacy AT Interface
Researchers from the University of Birmingham and Fuzzware demonstrated that a single malicious SIM card can issue proactive commands forcing cellular modules to execute arbitrary AT instructions. Testing of 26 devices revealed nine vulnerable units, including six out of eight cellular modules from Quectel used in EV chargers, industrial routers, and automotive T-Box systems. The attack leverages the long-standardized RUN AT proactive command introduced in 1981, which allows the SIM to instruct the modem and, in many cases, the application processor running Linux. Concrete exploits were shown on an Autel MAXI US AC W12-L-4G charger, an OPPO Reno 14 F 5G phone locked to 2G, and a Quectel EG25-G module enabling file exfiltration. Five vendors were notified in March 2026 yet none have issued public advisories as of August; the issues are tracked as CVE-2026-57550 and CVD-2026-0122. High Qualcomm-based modules remain widely deployed in critical infrastructure with no centralized visibility or uniform disablement mechanism.