Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-94pr-w968-h923

Jenkins Telegram Bot Plugin stores the Telegram Bot token in plaintext

CVSS 3.3 LowEPSS 0.0052 · 44th percentile

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

PackageEcosystemAffectedFixed in
org.jenkins-ci.plugins:telegrambotMaven<=1.4.0No fixed version yet
Identifiers
GHSA-94pr-w968-h923 · CVE-2024-34147
Weakness (CWE)
CWE-522
Tags
Published
2 May 2024
Updated
3 Jul 2024

Machine-written summary

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

The Jenkins Telegram Bot Plugin, versions 1.4.0 and earlier, stores the Telegram Bot token unencrypted in its global configuration file on the Jenkins controller. An attacker who can read the controller's file system, such as someone with local access to that host, can view the token. The source lists no fixed version, so no fix is available yet.

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
3.3 Low 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0052, the 44th 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.