Skip to main content
CVE-2025-49824VulnerabilityPublished

CVE-2025-49824: conda-smithy · Information Exposure

Affects conda-smithySource CVE Database V5

0

Not known to be exploited · CVSS 1.7 Low : upgrade to 3.47.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
1.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.47.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade conda-smithy to 3.47.1.

Affected software

ProductAffectedFixed in
PyPIconda-smithypkg:pypi/conda-smithyOther threatsAffected
  • <3.47.1
Fixed in
  • 3.47.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade conda-smithy to version 3.47.1 or later immediately to ensure the patched encryption scheme is in use. 2. Audit and rotate any Binstar or related authentication tokens that were generated or used with vulnerable versions of conda-smithy to prevent unauthorized reuse. 3. Restrict access to CI systems and any oracle endpoints that process encrypted tokens to trusted users and networks, minimizing the attack surface. 4. Implement monitoring and alerting for unusual access patterns or failed decryption attempts on CI services that could indicate exploitation attempts. 5. Review and harden CI/CD pipeline security, including enforcing least privilege for tokens and credentials, to limit the impact of any token exposure. 6. Educate development and DevOps teams about the importance of using updated tooling and promptly applying security patches in build environments.

Description

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.

References

Community reviews

Loading reviews…