Exploitation reportedFri, 6 Nov 2026
Airbyte Connector Builder exploitation: isolate the service and update by deployment type
JVN has confirmed exploitation of the Airbyte Connector Builder command-execution vulnerability. Restrict Builder access, preserve container records and plan a 2.2.0 update or vendor-assisted migration according to deployment type.
Article
On 2026/11/04, JVN confirmed exploitation of the Airbyte Connector Builder command-execution vulnerability. If enterprise data-integration containers can read source and destination credentials, compromise may affect data, synchronization jobs and reachable services.
The vendor identifies the vulnerability as GHSA-g35w-6r6v-h4r7 with CVSS v3.1 9.9. JVN separately lists CVSS v4.0 8.7 and v3.0 8.8, using different scoring vectors and scopes. Neither advisory lists a CVE identifier.
- 01
Builder reachable
2.x requires Reader privileges or higher; legacy Helm chart 1.x deployments may not require login
- 02
Malicious build content submitted
The affected Connector Builder or Manifest Server accepts the request
- 03
Commands executed in the container
Execution uses the Airbyte container user's privileges
- 04
Credentials and data at risk
Credentials, data and internal services accessible to the container may be accessed
Versions, patches and deployment exceptions
- JVN lists 1.7.0 through 2.1.0; the vendor lists versions before 2.2.0. The vendor's fix is Airbyte 2.2.0, including manifest-server/airbyte-cdk 7.23.7. No patch is provided for 1.x.
- 2.x requires Workspace Reader or Organization Reader privileges or higher. The 1.x Connector Builder using legacy Helm charts does not inherit authentication settings, so clients that can reach the service may exploit it without login. Disabling unsafe code does not remove the exposure.
- If an immediate update is not possible, allow only the Airbyte server to connect to Connector Builder or Manifest Server, and grant Reader privileges only to trusted users.
- Back up the database before upgrading to 2.2.0. Migration cannot be rolled back to 2.1.x. For users still running Self-Managed Enterprise, the vendor's 2.2 release notes say not to upgrade directly yet; contact an Airbyte representative to discuss moving to a Cloud plan.
- According to the vendor advisory, Airbyte Cloud customers do not need to take action.
- 01
Restrict Builder connections
Inventory internal, outsourced and container deployments. Allow only the Airbyte server to connect to Connector Builder or Manifest Server, and review Reader permissions.
See what to doResources: 2
TWISA member solutions
Restrict Builder connections
Inventory internal, outsourced and container deployments. Allow only the Airbyte server to connect to Connector Builder or Manifest Server, and review Reader permissions.
- 02
Update by deployment type
For generally applicable deployments, back up first, then follow the vendor's instructions to upgrade to 2.2.0 or a later patched version. Self-Managed Enterprise users should contact the vendor first to confirm a migration plan.
See what to doResources: 1
TWISA member solutions
Update by deployment type
For generally applicable deployments, back up first, then follow the vendor's instructions to upgrade to 2.2.0 or a later patched version. Self-Managed Enterprise users should contact the vendor first to confirm a migration plan.
- 03
Reduce data and credential permissions
Inventory source and destination credentials available to containers. Restrict database and service-account permissions, network egress and unnecessary mounts.
See what to doResources: 2
TWISA member solutions
Reduce data and credential permissions
Inventory source and destination credentials available to containers. Restrict database and service-account permissions, network egress and unnecessary mounts.
- 04
Investigate and recover from trusted sources
Preserve Builder, container, Kubernetes and data-system records. Review unusual commands, connections and exports. If compromise is suspected, isolate and rebuild, rotate credentials and retest synchronization jobs.
See what to doResources: 2
TWISA member solutions
Investigate and recover from trusted sources
Preserve Builder, container, Kubernetes and data-system records. Review unusual commands, connections and exports. If compromise is suspected, isolate and rebuild, rotate credentials and retest synchronization jobs.
Inventory versions, Helm charts, Reader permissions, containers, and source and destination connections
Allow authorized traffic and apply controls at each layer.
- 01
Service entry point
Airbyte server to Builder
Allow only necessary connectionsPrevent other sources from directly accessing Builder or Manifest Server
- 02
Container execution
Builder and synchronization-job containers
Patch and reduce permissionsUpdate by deployment type and restrict execution identities and mounts
- 03
Data connections
Source and destination databases
Least privilege for dataLimit readable and writable data, and separate credentials and network egress
Feed logs and traffic data from each layer into monitoring and response.
- Monitoring and recoveryCorrelate container, Kubernetes, identity and data-system records. Investigate unusual commands and data exports, and verify synchronization integrity after recovery.
Proactive testing and retesting
With authorization, perform asset discovery, vulnerability scanning, penetration testing, API testing and attack simulation. Verify Builder source reachability, authentication, container versions and data-system permissions, then retest after changes. If a separate website uses a WAF, independently verify request paths, alerts, actual blocking and backend results.
TWISA member solutions
Supporting: Restrict Builder connections
Applicable offer: ShareTech's NU-6000 next-generation firewall can support source restrictions in front of Builder services and management network segmentation. Through 2026/12/31, TWISA members can use code TWISA2026_ShareTech to apply for pricing at 95% of the listed price, with one year of AI IPS and AI Sandstorm protection and a 30-month hardware warranty. Apply through the vendor's form. This pairing concerns network source control; actual rules must match the deployment.
Inventory internal, outsourced and container deployments. Allow only the Airbyte server to connect to Connector Builder or Manifest Server, and review Reader permissions.
Supporting: Update by deployment type
For generally applicable deployments, back up first, then follow the vendor's instructions to upgrade to 2.2.0 or a later patched version. Self-Managed Enterprise users should contact the vendor first to confirm a migration plan.
Supporting: Reduce data and credential permissions
Inventory source and destination credentials available to containers. Restrict database and service-account permissions, network egress and unnecessary mounts.
Supporting: Investigate and recover from trusted sources
Preserve Builder, container, Kubernetes and data-system records. Review unusual commands, connections and exports. If compromise is suspected, isolate and rebuild, rotate credentials and retest synchronization jobs.
Official sources
- Airbyte: Connector Builder security advisory
- JVN: Airbyte command execution and confirmed exploitation
- Airbyte 2.2: deployment exceptions, backups and irreversible migration
Contact the relevant members for more detailed product and service information.
Advisory updated: 2026/11/06. Consult the vendor's latest information for product support and patch status.