CVE-2026-6580Public exploitNetwork attack vector

Amap API abuse via source-embedded key

Published Apr 19, 2026 · Updated Apr 19, 2026

Hard-coded credentials in liangliangyy DjangoBlog 2.1.0 allow remote attackers to obtain and abuse an Amap API key via OwnTracks. The Amap API call handler in owntracks/views.py passes a source-embedded key to the Amap reverse-geocoding API instead of loading a deployment-specific secret. Any party with repository access can reuse the exposed key for unauthorized Amap calls and location queries; no DjangoBlog account is required.

CVSS severity7.3
High
EPSS probability0.28%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded credentials in liangliangyy DjangoBlog 2.1.0 allow remote attackers to obtain and abuse an Amap API key via OwnTracks. The Amap API call handler in owntracks/views.py passes a source-embedded key to the Amap reverse-geocoding API instead of loading a deployment-specific secret. Any party with repository access can reuse the exposed key for unauthorized Amap calls and location queries; no DjangoBlog account is required.

The record

CVE
CVE-2026-6580
Published
Apr 19, 2026
Updated
Apr 19, 2026
Vendor
liangliangyy
Product
DjangoBlog
Classifications
CWE-321, CWE-320, T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

liangliangyy · DjangoBlogversion=2.1.0

Published CVSS scores

7.5VulDB CNA via NVDAV:N/AC:L/Au:N/C:P/I:P/A:P
7.3VulDB CNA via NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
5.5VulDB CNA via NVDCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
CWE-320Key Management Errors
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo