# CVE-2026-97230: IO::Socket::SSL::SelfCertificate versions 1.00 for Perl contains malware which executes Python code from an obfuscated URL.

> Malicious code in the IO::Socket::SSL::SelfCertificate Perl module executes arbitrary Python scripts from a remote URL, allowing attackers to run code on affected systems.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-559w-6g2v-jh67

## What is CVE-2026-97230?

CVE-2026-97230 is a critical vulnerability, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IO::Socket::SSL::SelfCertificate versions 1.00 for Perl contains malware which executes Python code from an obfuscated URL.

The generate_certificate runs a Python script saved as a certificate file.  The pyhton script attempts to retrieve code from a hardcoded http URL that is obfuscated with base64 encoding and run the response body directly.

The impact is that arbitrary code can be invoked as the user, without a dropped script being saved on the affected host.

The releases have no test scripts nor build hooks.  The intention may have been to trigger the payload after installation.

The dropper script is in lib/Crypt/SelfCertificate/sample/cert.pem.

This is similar to CVE-2026-95831 for the module Crypt::SelfCertificate.

The SHA-256 digests of the files are

    ba24ee8ec3b7f47f65bed62e16fb413ace50653cf44bd8ea90914390922831e0  IO-Socket-SSL-SelfCertificate-1.00.tar.gz
    821d38830e5eb8607738421c25ac25f59fff02a6ab67daa32fbd020429454dac  IO-Socket-SSL-SelfCertificate-1.00/lib/IO/Socket/SSL/SelfCertificate/sample/cert.pem

    d483cb7b23b7271cb11cf242bff4a2e1c02df0b9525eb0429abeea8961c399d5  IO-Socket-SSL-SelfCertificate-1.00-upload.tar.gz

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2026-97230?


## How do I fix CVE-2026-97230?

No fix has been published for CVE-2026-97230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97230 being exploited?

There is no known exploitation of CVE-2026-97230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97230 and fix it if it is affected.

What it is: CVE-2026-97230 is a critical vulnerability, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97230 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97230/ (Markdown: https://insights.sbomify.com/CVE-2026-97230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97230
- OSV: https://osv.dev/vulnerability/CVE-2026-97230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97230/
Summaries are generated and may contain mistakes; the official description above is the record.