{"id":"CVE-2020-26263","aliases":["GHSA-wvcv-832q-fjg7","PYSEC-2020-143"],"title":"RSA weakness in tslite-ng","summary":"RSA weakness in tslite-ng","severity":"high","cvss":7.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","vendor":"tlslite-ng","product":"tlslite-ng","ecosystem":"pip","affected":["tlslite-ng < 0.7.6"],"patched":["tlslite-ng 0.7.6"],"published":"2020-12-21","updated":"2026-07-08","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-wvcv-832q-fjg7","references":[{"url":"https://github.com/tlsfuzzer/tlslite-ng/security/advisories/GHSA-wvcv-832q-fjg7"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26263"},{"url":"https://github.com/tlsfuzzer/tlslite-ng/pull/438"},{"url":"https://github.com/tlsfuzzer/tlslite-ng/pull/439"},{"url":"https://github.com/tlsfuzzer/tlslite-ng/commit/c28d6d387bba59d8bd5cb3ba15edc42edf54b368"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tlslite-ng/PYSEC-2020-143.yaml"},{"url":"https://github.com/tlsfuzzer/tlslite-ng"},{"url":"https://pypi.org/project/tlslite-ng"},{"url":"https://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python"}],"tags":["osv","pip"],"epss":0.01523,"epssPercentile":0.73503,"ingestedAt":"2026-07-08T18:25:53.908Z","slug":"CVE-2020-26263","body":"## Overview\n\n### Impact\nThe code that performs decryption and padding check in RSA PKCS#1 v1.5 decryption is data dependant.\nIn particular, code in current (as of 0.8.0-alpha38) master\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/0812ed60860fa61a6573b2c0e18771414958f46d/tlslite/utils/rsakey.py#L407-L441\nand code in 0.7.5 branch\nhttps://github.com/tlsfuzzer/tlslite-ng/blob/acdde3161124d6ae37c506b3476aea9996d12e97/tlslite/utils/rsakey.py#L394-L425\nhas multiple ways in which it leaks information (for one, it aborts as soon as the plaintext doesn't start with 0x00, 0x02) about the decrypted ciphertext (both the bit length of the decrypted message as well as where the first unexpected byte lays).\n\nAll TLS servers that enable RSA key exchange as well as applications that use the RSA decryption API directly are vulnerable.\n\nAll previous versions of tlslite-ng are vulnerable.\n\n### Patches\nThe patches to fix it are proposed in \nhttps://github.com/tlsfuzzer/tlslite-ng/pull/438\nhttps://github.com/tlsfuzzer/tlslite-ng/pull/439\n\nNote: the patches depend on Python processing the individual bytes in side-channel free manner, this is known to not be the case: https://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\nAs such, users that require side-channel resistance are recommended to use different TLS implementations, as stated in the [security policy](https://github.com/tlsfuzzer/tlslite-ng/blob/master/SECURITY.md) of tlslite-ng.\n\n### Workarounds\nThere is no way to workaround this issue.\n\n### References\nhttps://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python/\n\n### For more information\nIf you have any questions or comments about this advisory please open an issue in [tlslite-ng](https://github.com/tlsfuzzer/tlslite-ng/issues).\n\n## Affected packages\n\n- `tlslite-ng < 0.7.6`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `tlslite-ng 0.7.6`","depth":"twilight","depthScore":42,"depthScoreParts":{"impact":41.3,"likelihood":0.3,"exploitation":0,"ransomware":0},"changes":[]}