← Back to results
Vulnerability record · public intelligence
CVE-2025-49824
LOW

conda-smithy Insecure Encryption Vulnerable to Oracle Padding Attack

Published Jun 17, 2025 · Updated Nov 3, 2026

Severity · CVSSLOW · Not scored
Known exploitationNot listed
EPSS / likelihood0.29%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

conda-smithy Insecure Encryption Vulnerable to Oracle Padding Attack

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

conda-smithy is a tool for combining a conda recipe with configurations to build using freely hosted CI services into a single repository. Prior to version 3.47.1, the travis_encrypt_binstar_token implementation in the conda-smithy package has been identified as vulnerable to an Oracle Padding Attack. This vulnerability results from the use of an outdated and insecure padding scheme during RSA encryption. A malicious actor with access to an oracle system can exploit this flaw by iteratively submitting modified ciphertexts and analyzing responses to infer the plaintext without possessing the private key. This issue has been patched in version 3.47.1.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Source repository ↗

Record history

Published Jun 17, 2025 · Last refreshed Nov 3, 2026