CVE-2019-25101

MEDIUMNVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 30% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability classified as critical has been found in OnShift TurboGears 1.0.11.10. This affects an unknown part of the file turbogears/controllers.py of the component HTTP Header Handler. The manipulation leads to http response splitting. It is possible to initiate the attack remotely. Upgrading to version 1.0.11.11 is able to address this issue. The patch is named f68bbaba47f4474e1da553aa51564a73e1d92a84. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220059.

CVSS v3
6.3
EG Score
6.3(medium)
EPSS
54.2%
KEV
Not listed

Published

February 4, 2023

Last Modified

November 21, 2024

References (10)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
turbogears0.5.0 ... 1.0.9 (21 versions)1.0.11.11—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 16:59 UTCEPSS rescore
  2. 2026-07-16 16:59 UTCEPSS rescore
  3. 2026-07-16 06:53 UTCOSV refresh
  4. 2026-07-15 16:55 UTCEPSS rescore
  5. 2026-07-15 16:55 UTCEPSS rescore
  6. 2026-07-13 22:27 UTCEPSS rescore
  7. 2026-07-13 06:10 UTCEPSS rescore
  8. 2026-07-13 06:10 UTCEPSS rescore
  9. 2026-07-12 05:43 UTCEPSS rescore
  10. 2026-07-12 05:43 UTCEPSS rescore
  11. 2026-07-11 08:24 UTCEPSS rescore
  12. 2026-07-11 08:24 UTCEPSS rescore
  13. 2026-07-09 19:06 UTCEPSS rescore
  14. 2026-07-08 15:11 UTCEPSS rescore
  15. 2026-07-07 13:43 UTCEPSS rescore
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-06 16:25 UTCEPSS rescore
  18. 2026-07-06 02:20 UTCEPSS rescore
  19. 2026-07-05 02:27 UTCEPSS rescore
  20. 2026-07-04 06:28 UTCEPSS rescore
  21. 2026-07-01 15:03 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-30 23:20 UTCEPSS rescore
  24. 2026-06-28 14:04 UTCEPSS rescore
  25. 2026-06-28 06:22 UTCOSV refresh
Show 56 more
  1. 2026-06-28 04:54 UTCEPSS rescore
  2. 2026-06-28 04:54 UTCEPSS rescore
  3. 2026-06-27 03:06 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-24 14:03 UTCEPSS rescore
  7. 2026-06-24 14:03 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-21 14:54 UTCEPSS rescore
  12. 2026-06-21 14:54 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-19 19:23 UTCEPSS rescore
  16. 2026-06-19 19:23 UTCEPSS rescore
  17. 2026-06-18 17:50 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
  26. 2026-06-10 22:16 UTCEPSS rescore
  27. 2026-06-10 17:17 UTCOSV refresh
  28. 2026-06-10 13:19 UTCEPSS rescore
  29. 2026-06-08 14:15 UTCEPSS rescore
  30. 2026-06-07 15:23 UTCEPSS rescore
  31. 2026-06-07 15:23 UTCEPSS rescore
  32. 2026-06-06 13:45 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-05 22:45 UTCEPSS rescore
  35. 2026-06-05 22:45 UTCEPSS rescore
  36. 2026-06-05 06:08 UTCEPSS rescore
  37. 2026-06-05 06:08 UTCEPSS rescore
  38. 2026-06-04 13:10 UTCEPSS rescore
  39. 2026-06-04 13:10 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-01 13:50 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-05-31 22:29 UTCEPSS rescore
  45. 2026-05-31 22:29 UTCEPSS rescore
  46. 2026-05-31 00:14 UTCEPSS rescore
  47. 2026-05-31 00:14 UTCEPSS rescore
  48. 2026-05-29 13:42 UTCEPSS rescore
  49. 2026-05-28 13:43 UTCEPSS rescore
  50. 2026-05-27 13:38 UTCEPSS rescore
  51. 2026-05-26 13:42 UTCEPSS rescore
  52. 2026-05-26 13:42 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore
  54. 2026-05-26 07:17 UTCEPSS rescore
  55. 2026-05-26 07:17 UTCEPSS rescore
  56. 2026-05-25 07:24 UTCEG score recompute

Frequently asked(5)

What is CVE-2019-25101?
CVE-2019-25101 is a medium vulnerability published on February 4, 2023. A vulnerability classified as critical has been found in OnShift TurboGears 1.0.11.10. This affects an unknown part of the file turbogears/controllers.py of the component HTTP Header Handler. The manipulation leads to http response splitting. It is possible to initiate the attack remotely.…
When was CVE-2019-25101 disclosed?
CVE-2019-25101 was first published in the National Vulnerability Database on February 4, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25101 actively exploited?
CVE-2019-25101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-25101?
CVE-2019-25101 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2019-25101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25101, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-25101

Explore →

Is Your Infrastructure Affected by CVE-2019-25101?

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

Start Free Scan →Browse All CVEs