Every 4 hours

Cyber

Original briefings from the security press, rewritten for operators. Each story keeps the date of the report it is based on, links the identifiers it discusses, and points back to the original publication.

Threat intelligence

Trackers and reporting desks followed on the same four-hour update. New public reports are rewritten into the briefings below.

PrioritySourceWebsiteInformation
Ransomware.liveWebsiteRansomware.liveInformationRansomware groups, victims, incidents
The DFIR ReportWebsiteThe DFIR ReportInformationDetailed intrusion investigations
SANS Internet Storm CenterWebsiteSANS ISCInformationAttack observations and incident analysis
abuse.ch ThreatFoxWebsiteThreatFoxInformationIndicators of compromise
abuse.ch URLhausWebsiteURLhausInformationMalware distribution infrastructure
abuse.ch MalwareBazaarWebsiteMalwareBazaarInformationMalware hashes and metadata
abuse.ch Feodo TrackerWebsiteFeodo TrackerInformationBotnet command-and-control infrastructure
AlienVault OTXWebsiteAlienVault OTXInformationCommunity threat-intelligence indicators
PhishTankWebsitePhishTankInformationPhishing intelligence
Shadowserver FoundationWebsiteShadowserverInformationInternet exposure and threat reporting
  1. Aug 17, 2026 · ZeroDay Catalog

    Critical Server-Side Request Forgery Vulnerability in MLflow

    A server-side request forgery vulnerability has been identified in MLflow versions prior to 3.15.0, potentially exposing sensitive internal services.

    What changed

    A server-side request forgery (SSRF) vulnerability was discovered in MLflow, affecting versions from 3.3.0 up to 3.14.0. The vulnerability arises from the handling of webhook URLs, which allows unauthorized users to exploit the system and access internal or cloud metadata services.

    The issue was addressed in version 3.15.0, which mitigates the risk by ensuring that the validated address is pinned and not subject to redirection.

    Who is affected

    Organizations utilizing MLflow for AI engineering and machine learning model management are at risk, particularly those running versions prior to 3.15.0.

    The vulnerability could impact any deployment of MLflow that uses the affected webhook endpoint, potentially exposing sensitive internal services.

    • MLflow users on versions 3.3.0 to 3.14.0
    • Organizations leveraging MLflow for AI and machine learning projects
    • Developers integrating MLflow with internal systems or cloud services

    What to do

    It is imperative for users of MLflow to upgrade to version 3.15.0 or later to mitigate the SSRF vulnerability. This update will ensure that the system is protected against unauthorized access to internal services.

    Additionally, organizations should review their webhook configurations and monitor for any unusual access patterns that may indicate exploitation attempts.

    • Upgrade MLflow to version 3.15.0 or later immediately.
    • Review and secure webhook configurations to prevent unauthorized access.
    • Monitor system logs for any suspicious activity related to webhook endpoints.

    Original report

  2. Aug 11, 2026 · ZeroDay Catalog

    Critical Authorization Vulnerability in Adobe Commerce and Magento

    Adobe Commerce and Magento have been identified with a critical vulnerability that could allow unauthorized access to sensitive resources, potentially leading to privilege escalation.

    What changed

    A new vulnerability has been discovered in Adobe Commerce and Magento, characterized as an Incorrect Authorization issue. This flaw could allow an attacker to escalate privileges and access sensitive resources without requiring any user interaction.

    Who is affected

    Organizations utilizing Adobe Commerce and Magento are at risk due to this vulnerability. It is crucial for users of these platforms to assess their exposure and implement necessary security measures.

    • Adobe Commerce users
    • Magento platform users
    • E-commerce businesses relying on Adobe solutions
    • Developers and administrators managing Adobe Commerce and Magento installations

    What to do

    It is recommended that affected organizations review their systems for the presence of this vulnerability. Immediate action should be taken to apply any available patches or updates from Adobe to mitigate potential risks.

    • Monitor for updates from Adobe regarding this vulnerability.
    • Implement security best practices to limit access to sensitive resources.
    • Conduct a security audit of your Adobe Commerce and Magento installations.
    • Educate staff about the implications of privilege escalation and unauthorized access.

    Original report