How broadly exploitable is this vulnerability?

Exploitability depends on an attacker's ability to access the encrypted data. If they can read appliance storage, backups, or configuration exports, the weak cryptography makes it feasible to recover credentials, even without knowledge of keys.

Does an attacker need existing privileges to exploit this?

Some level of access is typically required, such as file-system access, backup access, or authenticated access to an interface that exposes encrypted values. However, once ciphertext is obtained, the weakness of the algorithm significantly lowers the barrier to recovering plaintext.

What is the safest general fix pattern?

Replace the weak algorithm with a modern, vetted cryptographic primitive, use established libraries instead of custom schemes, and apply robust key management practices. Additionally, re-encrypt or re-store existing secrets and rotate any credentials that may have been exposed.

Severity:

HIGH RISK

(7.5)

Use of Weak Cryptographic Algorithm (CWE-327) in Cohesity TranZman Migration Appliance

CVE-2025-63912

Published:

Mar 3, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Use of Weak Cryptography

CWE:

CWE-327

Impact:

Credential Exposure and Unauthorized Access

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Use of Weak Cryptography

CWE:

CWE-327

Impact:

Credential Exposure and Unauthorized Access

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Use of Weak Cryptographic Algorithm (CWE-327) in Cohesity TranZman Migration Appliance

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare