This support forum is no longer in use. Please use the Cloudinary Community at to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

Log4j Vulnerability - Response Required


1 comment

  • Avatar
    Francis Tagbo

    Hi Kim,

    We fully understand your concern around this new, critical level, Log4j vulnerability. Especially as it was categorized as Critical with a CVSS score of 10 (the highest score possible). 

    Our security and operations teams immediately (Friday, Dec.10, 2021) reviewed all of our services and interfaces in order to map potential exposures.

    Our team managed to successfully validate that currently, we’re not aware of any potential exposure for this specific vulnerability. 

    In general, we believe in proactive security operations, meaning, we’ll keep evaluating the situation in order to verify we proactively mitigate potential related risks going forward.

    Best Regards,

    Comment actions Permalink

Post is closed for comments.