CVE-2025-14038
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEDB Hybrid Manager contains a flaw that allows an unauthenticated attacker to directly access certain gRPC endpoints. This could allow an attacker to read potentially sensitive data or possibly cause a denial-of-service by writing malformed data to certain gRPC endpoints. This flaw has been remediated in EDB Hybrid Manager 1.3.3, and customers should consider upgrading to 1.3.3 as soon as possible. The flaw is due to a misconfiguration in the Istio Gateway, which manages authentication and authorization for the affected endpoints. The security policy relies on an explicit definition of required permissions in the Istio Gateway configuration, and the affected endpoints were not defined in the configuration. This allowed requests to bypass both authentication and authorization within a Hybrid Manager service. All versions of Hybrid Manager - LTS should be upgraded to 1.3.3, and all versions of Hybrid Manager - Innovation should be upgraded to 2025.12.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEDB Hybrid Manager has an Istio Gateway misconfiguration where certain gRPC endpoints were omitted from the authentication and authorization policy definitions. This allowed unauthenticated attackers to bypass security controls, potentially accessing sensitive data or causing denial-of-service by writing malformed data to unprotected gRPC endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.3< 2025.12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed EDB Hybrid Manager versionCheck the running version of EDB Hybrid Manager using the product's admin UI, CLI tool, or by querying the deployed pods/containers. Common methods: 'helm list' for Helm deployments, 'kubectl get deployment' for Kubernetes, or check the application's /version endpoint if available.Affected if The installed version is lower than 1.3.3 or lower than 2025.12.0 (for innovation releases)
-
Determine if Istio Gateway is configuredInspect the Istio Gateway configuration in the cluster. For Kubernetes: 'kubectl get gateway -A' or 'kubectl describe gateway <gateway-name> -n <namespace>'. Check for gateway resources associated with the EDB Hybrid Manager namespace.Affected if An Istio Gateway resource exists and is routing traffic to EDB Hybrid Manager services
-
Review Istio AuthorizationPolicy for gRPC coverageCheck the Istio AuthorizationPolicy resources in the namespace where EDB Hybrid Manager is deployed: 'kubectl get authorizationpolicies -n <edb-hybrid-manager-namespace>' and inspect each policy's spec.selector or spec.rules to identify which services/endpoints are covered.Affected if AuthorizationPolicy exists but does not explicitly include gRPC service endpoints or the gRPC port (typically port 50051 or similar)
-
Verify gRPC endpoint exposureExamine the Kubernetes Service definitions for EDB Hybrid Manager: 'kubectl get svc -n <namespace>' and check for services exposing gRPC ports. Cross-reference with the Gateway listeners to confirm which ports are externally accessible.Affected if A Service exposes a gRPC port (e.g., port 50051, 8080, or custom) through the Istio Gateway without explicit authentication rules
-
Check for unauthenticated gRPC accessAttempt a test gRPC call to the exposed endpoints without providing credentials (mTLS certificate or JWT token). Use a tool like 'grpcurl' or 'grpcui' against the Gateway's external endpoint to probe for unauthenticated access.Affected if The gRPC endpoint accepts unauthenticated requests and returns valid responses instead of rejecting with authentication errors
A user is affected if EDB Hybrid Manager version is below 1.3.3 or below 2025.12.0 AND the Istio Gateway exposes gRPC endpoints without proper AuthorizationPolicy coverage, allowing unauthenticated access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.32025.12.0
Upgrade EDB Hybrid Manager to version 1.3.3 (LTS) or 2025.12 (Innovation) to remediate the Istio Gateway misconfiguration that allowed unauthenticated access to gRPC endpoints.
Hybrid Manager LTS: 1.3.3; Hybrid Manager Innovation: 2025.12
- Identify which Hybrid Manager variant is in use (LTS or Innovation)
- For Hybrid Manager - LTS: upgrade to version 1.3.3 or later
- For Hybrid Manager - Innovation: upgrade to version 2025.12 or later
- After upgrade, verify that gRPC endpoints require authentication as expected
- Confirm the Istio Gateway configuration now properly defines the affected endpoints with authentication policies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14038 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data