CVE-2026-55506

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129277 (ENISA EUVD)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wavelog is web-based amateur radio logging software. Prior to 2.5, the filename parameter accepted by POST /qsl/addQsoToQsl in application/controllers/Qsl.php addQsoToQsl() is stored without rejecting directory separators or relative path components, and POST /qsl/delete reaches application/models/Qsl_model.php deleteQsl(), which passes the planted qsl_images filename to unlink(). A standard authenticated user can associate the malicious filename with the user's own QSO, satisfy the ownership check, escape the per-user QSL image directory, and delete files writable by the PHP worker. Deleting configuration or operational files can cause denial of service, while deleting installer gate files can reopen the unauthenticated installer and enable application identity takeover through attacker-controlled database configuration. This issue is fixed in version 2.5.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 19, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

Version 2.5

Patch available: wavelog/wavelog 2.5

https://github.com/wavelog/wavelog/releases/tag/2.5
GitHub commit Patch Available

commit 73023a2cdda5 (wavelog/wavelog)

Patch available: wavelog/wavelog 2.5 (contains commit 73023a2cdda5)

https://github.com/wavelog/wavelog/commit/73023a2cdda5ef9b0c2f1b8a09bbd5a5fc2f1a80
GitHub pull request Patch Available

Fix qsl stuff

Patch available: wavelog/wavelog 2.5 (PR #3250 merged 2026-05-20)

https://github.com/wavelog/wavelog/pull/3250
GitHub advisoryMentions a patch (unverified)

Authenticated Arbitrary File Deletion via QSL Image Filename Path Traversal · Advisory · wavelog/wavelog · GitHub

https://github.com/wavelog/wavelog/security/advisories/GHSA-gxjg-q5fc-94q3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 19:22 UTCEchelonGraph re-scored
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-11-20 17:51 UTCEchelonGraph re-scored
  4. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-11-19 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-11-19 16:30 UTCEchelonGraph re-scored
  7. 2026-11-19 16:03 UTCEchelonGraph re-scored
  8. 2026-11-18 22:03 UTCENISA EUVD ID recordedEUVD-2026-129277 · Source: ENISA EUVD
  9. 2026-11-18 21:28 UTCEchelonGraph re-scored
  10. 2026-11-18 20:48 UTCEchelonGraph re-scoredFirst assessed: 9.6 CRITICAL
  11. 2026-11-18 20:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55506?
CVE-2026-55506 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Wavelog is web-based amateur radio logging software. Prior to 2.5, the filename parameter accepted by POST /qsl/addQsoToQsl in application/controllers/Qsl.php addQsoToQsl() is stored without rejecting directory separators or relative path components, and POST /qsl/delete reaches…
When was the CVE record for CVE-2026-55506 published?
The CVE record for CVE-2026-55506 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-55506 actively exploited?
CVE-2026-55506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55506?
CVE-2026-55506 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55506?
A fix for CVE-2026-55506 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55506

Explore →

Is Your Infrastructure Affected by CVE-2026-55506?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.