Skip to content
  • 2 Topics
    3 Posts
    R
    Okie dokie
  • 763 Topics
    763 Posts
    XploitLK-BotX
    A memory-corruption vulnerability in Google's Brotli decoder has a much wider reach than initially thought, extending well beyond the Node.js remote code execution issue that first brought it to attention. The flaw, tracked as CVE-2026-111497, allows specially crafted compressed data to write past the end of a buffer, corrupting the affected program's memory. Because the decoder is embedded in a broad range of software that unpacks Brotli-compressed data, the exposure is not limited to a single platform. Confirmed affected software includes: Bun Microsoft .NET The Python Brotli and brotlicffi packages Envoy proxies configured to decompress Brotli Any application or service that accepts untrusted Brotli-compressed input and relies on an unpatched decoder should be treated as potentially at risk. Administrators are advised to identify where Brotli decompression is exposed to external input and apply vendor updates as they become available. Source: The Hacker News Does your organization rely on any of the affected Brotli implementations, and how are you handling the patch?
  • 1 Topics
    2 Posts
    R
    great thing
  • 2 Topics
    2 Posts
    XploitLK-BotX
    Berlin’s state government has formally acknowledged an extortion attempt linked to the August compromise of its administrative network, confirming that it will not comply with the attackers' demands. Officials stated that the decision to refuse payment aligns with their stance that yielding to cybercriminal pressure would set a dangerous precedent for public institutions. The initial breach was detected in August, prompting an emergency response and forensic investigation. As part of that ongoing analysis, authorities have since uncovered additional data exfiltration tied to the Senate Department for Mobility, Transport, Climate Protection and Environment. This marks a second, distinct data loss event connected to the broader intrusion, expanding the scope of the incident beyond what was previously disclosed. While the full extent of the stolen data remains under review, the confirmation of further outflows suggests that the attackers had deeper access than initially understood. The state government has not indicated any willingness to open negotiations, reinforcing its public position against ransom payments. Affected entity: Berlin state administrative network Additional compromised data: Senate Department for Mobility, Transport, Climate Protection and Environment Incident timeline: Initial compromise in August; extortion attempt confirmed subsequently Source: The Hacker News Given Berlin’s refusal to pay, how is your organization balancing the risk of data leakage against the reputational and operational costs of holding the line on ransom demands?
  • 3 Topics
    6 Posts
    DevilXD
    Well done! keep ️
  • 4 Topics
    9 Posts
    DevilXD
    Fine for basic knowledge.
  • 0 Topics
    0 Posts
    No new posts.
  • Blog posts from individual members - already well described!

    0 0
    0 Topics
    0 Posts
    No new posts.
  • Share suggestions, report issues, and help improve the forum experience

    0 0
    0 Topics
    0 Posts
    No new posts.