CVE-2026-129467

Description

GeoPulse 1.5.0 through 2.3.0 contains an insecure direct object reference vulnerability in GET /api/v1/places/geocoding/{id} that allows authenticated users to read other users' private locations. Attackers can enumerate sequential reverse_geocoding_location ids to retrieve other users' custom place names, city, country, coordinates and bounding boxes from their history.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 5.3CVSS 4.0, Mediumfrom the CNA (VulnCheck)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
• 4.3CVSS 3.1, Mediumfrom the CNA (VulnCheck)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 15 Nov 2026 Published

Weakness

• CWE-639

References

• hackmd.iothird-party-advisory
• github.comissue-tracking
• github.compatchissue-tracking
• github.compatch
• github.comtechnical-description
• VulnCheck Advisory: GeoPulse 1.5.0 through 2.3.0 IDOR via Geocoding Place-Details Endpointthird-party-advisory