Skip to main content
Menu
CVEs

AperiSolve denial of service in PNG repair via crafted upload

CVE-2026-77336Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.4.2
Who is exposed
Not reported

Summary

Aperi'Solve, a steganalysis web platform from Zeecka, can be made to waste processing time when it handles a specially crafted PNG upload. An attacker can reach the flaw remotely and without logging in, by submitting a malformed PNG that ties up a worker and can delay or block image analysis for other users.

Written by a model

Original description

Aperi'Solve is an open-source steganalysis web platform. Prior to 3.4.2, an unauthenticated user can submit a PNG to POST /upload, which reaches aperisolve/utils/png.py through analyze_image, PCRTAnalyzer, PNG.repair(), and check_idat(). A malformed IDAT chunk can make attacker-controlled length and newline data drive an unbounded combinations search in PNG._fix_dos2unix(), causing repeated CRC checks that occupy a worker and delay or block image analysis for other users. Per-IP upload limits and eventual job termination bound the denial of service, and the issue has no confidentiality or integrity impact. This issue is fixed in version 3.4.2.

What to do

Upgrade to a fixed version: 3.4.2.

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-2026-77336 (Aperi'Solve: Uncontrolled resource consumption in PNG "repair" (PCRT): a sub-100-byte upload pins a worker CPU (DoS)), 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-2026-77336 (entry last updated 2026-11-19):
Affected:
- Zeecka AperiSolve: fixed in 3.4.2
Fixed versions: 3.4.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77336 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77336 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://github.com/Zeecka/AperiSolve/security/advisories/GHSA-f7j8-f987-jw98
- https://github.com/Zeecka/AperiSolve/commit/146985d89c62410a522294493a9c679d0cc49e9c
- https://github.com/Zeecka/AperiSolve/releases/tag/3.4.2
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-2026-77336
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-2026-77336"}.

Affected versions

cve.now Index

22Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

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

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Zeecka/AperiSolve · Advisory GHSA-f7j8-f987-jw98
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77336
RecordNVD · CVE-2026-77336
Other links 2
RepositoryGitHub · Zeecka/AperiSolve · Commit 146985d8
RepositoryGitHub · Zeecka/AperiSolve · Release 3.4.2

Questions about CVE-2026-77336

Is CVE-2026-77336 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-2026-77336?

AperiSolve: before 3.4.2.

Source: cve.now feed data

How do I fix CVE-2026-77336?

Upgrade to a fixed version: 3.4.2.

Source: cve.now feed data

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