# CVE-2011-10043: Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded

> Attackers can execute arbitrary code by passing malicious module names to the load function in vulnerable Perl Module::Load versions.

- **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:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** DEBIAN-CVE-2011-10043, GHSA-8x3h-9qcg-hv3j, UBUNTU-CVE-2011-10043

## What is CVE-2011-10043?

CVE-2011-10043 is a critical code injection vulnerability in BINGOS Module::Load, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded.

Module names starting with "::" could be passed to the load function to specify arbitrary module paths.

Attackers able to influence module names passed to load could use that bug to execute arbitrary code.

Weakness: CWE-145 (Improper Neutralization of Section Delimiters)

## Which versions are affected by CVE-2011-10043?


## How do I fix CVE-2011-10043?

Upgrade to a fixed version.

## Is CVE-2011-10043 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-10043 and fix it if it is affected.

What it is: CVE-2011-10043 is a critical code injection vulnerability in BINGOS Module::Load, published on 7 Jul 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-2011-10043 in the wild and no public exploit code.

Affected product: BINGOS Module::Load. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2011-10043/ (Markdown: https://insights.sbomify.com/CVE-2011-10043/index.md)
```

## Sources

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

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