---
title: Svix is NOT affected by the Log4j vulnerability
authors: ['tom']
date: 2021-12-15T12:00:00
tags: ['Security']
summary: We just wanted to share a quick update to let you know that Svix is NOT affected by the Log4j vulnerability.
---

![Cover image](./cover.jpg)

TL;DR: Svix is NOT affected by the Log4j vulnerability.

A newly discovered vulnerability impacting Apache Log4j was made public recently. You can read more information about the issue [on the lunasec blog](https://www.lunasec.io/docs/blog/log4j-zero-day/), though the gist is: it affects most Java applications out there, and given that Java is quite popular, it affects a lot of services.

We just wanted to share a quick update that we are aware of the vulnerability, and have completed the verification and impact assessment the moment it became public. We do not use Java (or Log4j) anywhere in our production environments and services, so there has been no impact on either us or our customers. Just to repeat it again: **Svix is not impacted by this vulnerability**.

That's it for this update, we just wanted to make sure our customers know that their data is safe and Svix has not been affected.

Make sure to follow us on [Twitter](https://twitter.com/SvixHQ), [Mastodon](https://mastodon.social/@svixhq), [Github](https://github.com/svix) or [RSS](https://www.svix.com/blog/rss/) for the latest updates for the [Svix webhook service](https://www.svix.com), or join the discussion on [our community Slack](https://www.svix.com/slack/).