# CVE-2018-25160: Code injection in HTTP::Session2

> Attackers can inject code via session IDs in HTTP::Session2 if the backend allows it, requiring specific session storage configurations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-hg4g-pqvm-c557

## What is CVE-2018-25160?

CVE-2018-25160 is a medium-severity code injection vulnerability in TOKUHIROM HTTP::Session2, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend.

For example, if an application uses memcached for session storage, then it may be possible for a remote attacker to inject memcached commands in the session id value.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-25160?

It affects 1 product.


Products: Tokuhirom Http\.

## How do I fix CVE-2018-25160?

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

## Is CVE-2018-25160 being exploited?

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

## Other vulnerabilities in TOKUHIROM HTTP::Session2

- [CVE-2026-3255](https://insights.sbomify.com/CVE-2026-3255/): HTTP::Session2 versions before 1.12 for Perl may generate weak session ids using the rand() function (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25160 and fix it if it is affected.

What it is: CVE-2018-25160 is a medium-severity code injection vulnerability in TOKUHIROM HTTP::Session2, published on 27 Feb 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-2018-25160 in the wild and no public exploit code.

Affected product: TOKUHIROM HTTP::Session2. 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-2018-25160/ (Markdown: https://insights.sbomify.com/CVE-2018-25160/index.md)
```

## Sources

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

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