CVE-2014-6274

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-06-26. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes was set, and the remote used encryption=pubkey or encryption=hybrid, the embedded AWS credentials were stored in the git repository in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
5.0%
KEV
Not listed

Published

June 26, 2025

Last Modified

August 6, 2025

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2014-6274?
CVE-2014-6274 is a high vulnerability published on June 26, 2025. git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes was set, and the remote used encryption=pubkey or encryption=hybrid, the embedded AWS credentials were stored in the git repository in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects…
When was CVE-2014-6274 disclosed?
CVE-2014-6274 was first published in the National Vulnerability Database on June 26, 2025, with the most recent update on August 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-6274 actively exploited?
CVE-2014-6274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2014-6274?
CVE-2014-6274 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2014-6274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-6274, 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

Explore the affected products and dependency analysis for CVE-2014-6274

Explore →

Is Your Infrastructure Affected by CVE-2014-6274?

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

Start Free Scan →Browse All CVEs