Skip to main content
Menu
CVEs

reminiscence OS command injection in HTML-to-PDF conversion

CVE-2022-4998Published November 21, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

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

Original 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 systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

13Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2022-4998
RecordNVD · CVE-2022-4998
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitgist.github.com · hoehyeonlab/3c7159db2556c415ad9ac6ea1202347c
Other links 4
AdvisoryVulDB · Advisory #440643
AdvisoryVulDB · Threat intelligence #440643
AdvisoryVulDB · CVE-2022-4998 record
AdvisoryVulDB · Submission #1046157

Questions about CVE-2022-4998

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: cve.now feed data

Which versions are affected by CVE-2022-4998?

reminiscence: version 0.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.