@kapa.ai We’ve deployed the core version of Airbyte and are currently running the Airbyte 2.0 release. During routine container scanning, we observed several OS‑level vulnerabilities that appear to originate from Airbyte‑provided images, specifically the Java base image. I am following the reporting format described in your security documentation: Security | Airbyte Docs. I have sent all the details in email -> security@airbyte.io but i am not getting a response. Any other way to reach out to Airbyte security team to get these vulnerabilities addressed ?

Thinking completed You've followed the correct process by emailing security@airbyte.io. Beyond that, the knowledge sources suggest a couple of additional avenues: 1. Airbyte Community Slack — Join slack.airbyte.com and ask in a relevant channel. However, be cautious not to share sensitive vulnerability details publicly there. [Reporting Vulnerabilities] 2. If you're an Airbyte Cloud/paid customer — Open a support ticket at support.airbyte.com and reference your email to security@airbyte.io. [Issues and Requests] A few important reminders from Airbyte's security policy: • Do not file a public GitHub issue or post in the public forum for undisclosed vulnerabilities, as this could lead to additional security risks. [Reporting Vulnerabilities] • The security email is intended specifically for undisclosed vulnerabilities — which matches your situation. Regarding the underlying issue itself, there is an open GitHub issue from another community member raising similar concerns about OS-level vulnerabilities in Airbyte 2.0 Docker images. Airbyte's team acknowledged it and escalated it internally, but noted no guaranteed response timeline for community-reported issues. [Security Updates Issue] Recommendation: If you haven't heard back via email after a reasonable period, try following up on that same email thread, and if you're a paid customer, escalate via the support portal referencing your original security email. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I have tried following up on that same email thread but no luck

Thinking completed I'm sorry to hear that. Unfortunately, the knowledge sources do not provide any additional dedicated security escalation channels beyond what has already been suggested. However, here are the remaining options available to you: • Airbyte Community Slack (slack.airbyte.com) — You could reach out there and ask a maintainer to help escalate your unanswered security email internally, without disclosing the vulnerability details publicly. [Reporting Vulnerabilities] • Support portal — If you are an Airbyte Cloud or Enterprise customer, open a ticket at support.airbyte.com and explicitly reference your unanswered email to security@airbyte.io, asking for it to be escalated. [Securing Airbyte Cloud] • Airbyte Trust Center — The Airbyte Trust Center is mentioned in the security documentation and may have additional contact or escalation options for security-related concerns. [Security] Beyond these, the knowledge sources do not contain enough information to point to any other escalation path for unresponsive security reports. Your best bet is likely a combination of the Community Slack (to get maintainer attention) and the support portal if you have a paid relationship with Airbyte. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.