22 matches found
GO-2026-6865 vulnerabilities
Vulnerabilities for packages: conftest, juicefs, gomplate, cortex, verticadb-operator, migrate, k6, sftpgo, caddy, thanos, kaf, datadog-operator, kyverno, victoriametrics-operator, flux-source-controller, local-path-provisioner, cosign, flyte, steampipe, kafkaexporter, telegraf, kubescape,...
CVE-2026-116591 vulnerabilities
Vulnerabilities for packages: conftest, juicefs, gomplate, cortex, verticadb-operator, migrate, k6, sftpgo, caddy, thanos, kaf, datadog-operator, kyverno, victoriametrics-operator, flux-source-controller, local-path-provisioner, cosign, flyte, steampipe, kafkaexporter, telegraf, kubescape,...
GHSA-FPMH-FRQ8-7RJ8 vulnerabilities
Vulnerabilities for packages: conftest, juicefs, gomplate, cortex, verticadb-operator, migrate, k6, sftpgo, caddy, thanos, kaf, datadog-operator, kyverno, victoriametrics-operator, flux-source-controller, local-path-provisioner, cosign, flyte, steampipe, kafkaexporter, telegraf, kubescape,...
GO-2024-2918 vulnerabilities
Vulnerabilities for packages: goreleaser, hugo, cortex, zarf, sops, trino, flux-image-reflector-controller, zot, sigstore-scaffolding, up, nuclei, thanos, py3-cassandra-medusa, velero, step, sqlpad, chezmoi, opentelemetry-collector, argo-workflows, timestamp-authority, pulumi, argo-events, airflo...
GO-2025-3955 vulnerabilities
Vulnerabilities for packages: conftest, thanos-operator, nri-nginx, nats-server-config-reloader, wait-for-port, yunikorn-k8shim, ini-file, kor, migrate, rabbitmq-messaging-topology-operator, oauth2-proxy, caddy, aactl, cloud-provider-gcp-cloud-controller-manager, dex, headlamp, steampipe, hubble,...
GHSA-W879-237Q-WC7R vulnerabilities
Vulnerabilities for packages: gomplate, external-secrets-operator, kargo, terraform-provider-azurerm, caddy, kaf, aactl, kyverno, flux-source-controller, cosign, steampipe, telegraf, flux-notification-controller, fscrypt, splunk-otel-collector, kubescape, buildkitd, flux-kustomize-controller,...
GHSA-Q9HV-HPM4-HJ6X vulnerabilities
Vulnerabilities for packages: gomplate, crossplane-provider-aws-elasticache, gitaly, terraform-provider-azurerm, aactl, argo-workflows, crossplane-provider-aws-cloudfront, crossplane-provider-aws-rds, kyverno, flux-source-controller, flux-notification-controller, kubescape, buildkitd,...
CVE-2026-1229 vulnerabilities
Vulnerabilities for packages: gomplate, crossplane-provider-aws-elasticache, gitaly, terraform-provider-azurerm, aactl, argo-workflows, crossplane-provider-aws-cloudfront, crossplane-provider-aws-rds, kyverno, flux-source-controller, flux-notification-controller, kubescape, buildkitd,...
CVE-2026-1229 vulnerabilities
Vulnerabilities for packages: crossplane, terraform-provider-pagerduty-fips, crossplane-provider-aws-cognitoidentity-fips, policy-controller-fips, crossplane-provider-aws-lambda, openbao, crossplane-provider-aws-iam, flux-image-automation-controller-fips, tekton-pipelines-fips,...
CVE-2021-38599
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
GHSA-VRMR-F2QH-3HHF Improper use of cryptographic key in wal-g
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
Improper use of cryptographic key in wal-g
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
Information Disclosure
github.com/wal-g/wal-g is vulnerable to information disclosure. The vulnerability exists when user uses libsodium encryption for their backup files which is not available but are silently processed and uploaded as plaintext...
CVE-2021-38599
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
CVE-2021-38599
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
Code injection
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
CVE-2021-38599
CVE-2021-38599 affects WAL-G prior to version 1.1. In non-libSodium builds, WAL-G silently ignores the libsodium encryption key and uploads backups in plaintext, creating an information disclosure vulnerability. Affected software: WAL-G backup tool (used with PostgreSQL, MySQL/MariaDB, MS SQL Ser...
CVE-2021-38599
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
CVE-2021-38599
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...
CVE-2021-38599: Improper Check for Unusual or Exceptional Conditions
WAL-G before 1.1, when a non-libsodium build e.g., one of the official binary releases published as GitHub Releases is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to...