Advisory record · GHSA-cp2c-x2pc-fph7

Apache SeaTunnel Web Authentication vulnerability

CVSS 8.2 HighEPSS 0.0072 · 54th percentile

Published by the GitHub Advisory Database at 30 Jul 2024, 09:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.seatunnel:seatunnel-webMaven<1.0.11.0.1
Identifiers
GHSA-cp2c-x2pc-fph7 · CVE-2023-48396
Weakness (CWE)
CWE-290
Published
30 Jul 2024
Updated
30 Jul 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache SeaTunnel Web (seatunnel-web) versions before 1.0.1 hardcode the JWT signing key in the application, so an attacker can forge tokens and log in as any user. The source describes the key as readable from the application configuration file, and this issue is listed as affecting version 1.0.0. Upgrade to seatunnel-web 1.0.1, which fixes the issue.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0072, the 54th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.