Skip to main content

Is someone able to provide the following in relation to Log4j and airtable



  • Is any of your infrastructure or your application affected?


Have you applied patching or mitigations?


Have you experienced any compromise of your systems / infrastructure?

I agree, given that log4shell is one of the most critical, wide-ranging security vulnerabilities ever… it seems that a formal statement from AirTable regarding their susceptibility to this issue is warranted.


While nothing is running locally for customers, customers should have assurances that data/service is not at risk from log4Shell. It is very, very concerning that AirTable has not bothered to respond to this critical concern weeks ago. Note that large enterprises simply want a statement from each vendor - this is something that AirTable should have already provided.


Reply