# CVE-2019-9081: Laravel Framework Deserialization Vulnerability


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Feb 2019
- **Updated:** 19 Aug 2022
- **Also known as:** GHSA-pfg4-p438-p874

## What is CVE-2019-9081?

CVE-2019-9081 is a vulnerability in laravel/framework, published on 24 Feb 2019. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none

## Which versions are affected by CVE-2019-9081?

2 open source packages ship an affected version, including laravel/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `laravel/framework` | Packagist | From 5.7.0 | 6.20.44 |
| `laravel/framework` | Packagist | From 5.7.0 | 6.20.44 |

## How do I fix CVE-2019-9081?

Upgrade laravel/framework to 6.20.44 or later.

## Is CVE-2019-9081 being exploited?

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

Public exploit code:

- PoC for CVE-2019-9081 (github_poc): https://github.com/nth347/CVE-2019-9081_PoC
- https://github.com/scopion/cve-2019-9081 (github_poc): https://github.com/scopion/cve-2019-9081
- https://github.com/qafdevsec/CVE-2019-9081_PoC (github_poc): https://github.com/qafdevsec/CVE-2019-9081_PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9081 and fix it if it is affected.

What it is: CVE-2019-9081 is a vulnerability in laravel/framework, published on 24 Feb 2019. 
Exploitation: There is no known exploitation of CVE-2019-9081 in the wild and no public exploit code.

Affected packages and fixed versions:
- laravel/framework (Packagist): affected from 5.7.0; fixed in 6.20.44
- laravel/framework (Packagist): affected from 5.7.0; fixed in 6.20.44

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

## Sources

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

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