Volkswagen car-location data-exposure incident - Revision history

Neige at 02:26, 6 June 2026

2026-06-06T02:26:53Z

← Older revision		Revision as of 02:26, 6 June 2026
Line 11:		Line 11:
	\|Description=Volkswagen suffered a large databreach, revealing customer's location data, battery statistics, and sensitive personal information.		\|Description=Volkswagen suffered a large databreach, revealing customer's location data, battery statistics, and sensitive personal information.
	}}		}}
	In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://web.archive.org/web/20260330070402/https://cybersecuritynews.com/volkswagen-data-breach/ Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.		In 2024, [[Volkswagen]] experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://web.archive.org/web/20260330070402/https://cybersecuritynews.com/volkswagen-data-breach/ Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.

	==Background==		==Background==

SomebodyThatMayContribute: Replaced cite "Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" from archive.ph to IA (archived it today)

2026-03-30T07:10:34Z

Replaced cite "Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" from archive.ph to IA (archived it today)

← Older revision		Revision as of 07:10, 30 March 2026
Line 11:		Line 11:
	\|Description=Volkswagen suffered a large databreach, revealing customer's location data, battery statistics, and sensitive personal information.		\|Description=Volkswagen suffered a large databreach, revealing customer's location data, battery statistics, and sensitive personal information.
	}}		}}
	In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/~~tVDzM~~ Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.		In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://web.archive.org/web/20260330070402/https://cybersecuritynews.com/volkswagen-data-breach/ Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.

	==Background==		==Background==

Sojourna: /* The incident */

2026-03-09T03:30:53Z

The incident

← Older revision		Revision as of 03:30, 9 March 2026
Line 18:		Line 18:

	==The incident==		==The incident==
	[[File:Volkswagen.png\|alt=Pie ~~Chart~~ showing the total cars affected including the severity of each(whether its location was exposed down to a radius of 10cm or 10km) and breakdown by brand\|thumb\|Pie ~~Chart~~ showing the total cars affected and breakdown by brand]]		[[File:Volkswagen geo-location pie chart.png\|alt=Pie chart showing the total cars affected including the severity of each(whether its location was exposed down to a radius of 10cm or 10km) and breakdown by brand\|thumb\|Pie chart showing the total cars affected and breakdown by brand]]
	The core issue stemmed from a misconfiguration in Volkswagen's AWS storage implementation, which left customer data publicly accessible without proper authentication or access restrictions<ref name=":0" />. This exposed sensitive information about vehicle locations, EV-battery statistics and sensitive customer information. The incident not only breached customer trust, but Volkswagen's own [[Terms of Service]].		The core issue stemmed from a misconfiguration in Volkswagen's AWS storage implementation, which left customer data publicly accessible without proper authentication or access restrictions<ref name=":0" />. This exposed sensitive information about vehicle locations, EV-battery statistics and sensitive customer information. The incident not only breached customer trust, but Volkswagen's own [[Terms of Service]].

	==Industry context==		==Industry context==

Bythmusters: Added cargo template

2026-01-14T01:19:24Z

Added cargo template

@@ Line 1: / Line 1: @@
 {{OngoingEvent}}
+{{IncidentCargo
 In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.

AnotherConsumerRightsPerson: wrong template

2025-10-26T17:59:53Z

wrong template

← Older revision		Revision as of 17:59, 26 October 2025
Line 1:		Line 1:
			{{OngoingEvent}}

	~~''Note: This article represents an ongoing situation and may be updated as more information becomes available.''~~

	In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.		In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.

Mr Pollo: Removing under development template after months of no progress

2025-08-11T22:22:50Z

Removing under development template after months of no progress

← Older revision		Revision as of 22:22, 11 August 2025
Line 1:		Line 1:
	~~{{Under_Development~~
	~~\|date=January 2025~~
	~~\|stage=early~~
	~~\|priority=high~~
	}}

	''Note: This article represents an ongoing situation and may be updated as more information becomes available.''		''Note: This article represents an ongoing situation and may be updated as more information becomes available.''

Kostas: add category

2025-01-28T17:23:59Z

add category

← Older revision		Revision as of 17:23, 28 January 2025
Line 63:		Line 63:
	[[Category:CARIAD]]		[[Category:CARIAD]]
	[[Category:Incidents]]		[[Category:Incidents]]
			[[Category:Articles based on videos]]

BobBarone: /* References */

2025-01-27T00:14:15Z

References

← Older revision		Revision as of 00:14, 27 January 2025
Line 23:		Line 23:
	==Regulatory response==		==Regulatory response==

	The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems.<ref>https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/vehicle_cybersecurity_best_practices_01072021.pdf</ref><!-- I couldn't find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. -->		The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems.<ref>https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/vehicle_cybersecurity_best_practices_01072021.pdf. [https://web.archive.org/web/20210720041841/https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/vehicle_cybersecurity_best_practices_01072021.pdf Archived] from the original on July 20, 2021. Retrieved January 27, 2025.</ref><!-- I couldn't find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. -->

	==Broader implications==		==Broader implications==

Mingyee: Added reference

2025-01-23T14:13:10Z

Added reference

← Older revision		Revision as of 14:13, 23 January 2025
Line 23:		Line 23:
	==Regulatory response==		==Regulatory response==

	The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems.~~{{Citation needed\|date=January 2024\|reason=Letter reference needed}}~~<!-- I couldn't find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. -->		The National Highway Traffic Safety Administration (NHTSA) has previously expressed concerns about automotive data security. Following the 2020 Massachusetts Right to Repair initiative, NHTSA official Carrie Gules issued a letter addressing potential security vulnerabilities in vehicle data systems.<ref>https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/vehicle_cybersecurity_best_practices_01072021.pdf</ref><!-- I couldn't find any specific letter that was referenced here, although there have been some sources saying that the NHTSA has taken part in Massachusetts Right to Repair regulations. -->

	==Broader implications==		==Broader implications==

Mingyee: Fixed link

2025-01-23T14:10:13Z

Fixed link

← Older revision		Revision as of 14:10, 23 January 2025
Line 4:		Line 4:
	\|priority=high		\|priority=high
	}}		}}

			''Note: This article represents an ongoing situation and may be updated as more information becomes available.''

	In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.		In 2024, Volkswagen experienced a data-security incident involving customer vehicle information stored on [[Amazon Web Services]] (AWS). The incident occurred when Volkswagen's implementation of [[CARIAD]], a system used for storing terabytes of customer data, was discovered to have publicly accessible storage instances, because of a misconfiguration<ref name=":0">[https://cybersecuritynews.com/volkswagen-data-breach/]"Volkswagen Data Breach: 800,000 Electric Car Owners’ Data Leaked" written by Guru Baran (co-founder of Cyber Security News and GBHackers On Security). [https://archive.ph/tVDzM Archived] from the original on December 28, 2024. Retrieved on January 15, 2025.</ref>.

	==Background==		==Background==

Line 37:		Line 40:
	*Drive times		*Drive times

	==See ~~Also~~==		==See also==
	*Data privacy		*Data privacy
	*[[Right to repair]]		*[[Right to repair]]
Line 43:		Line 46:
	*[[Volkswagen]]		*[[Volkswagen]]
	*[[2020 Massachusetts Right to Repair ballot initiative]]		*[[2020 Massachusetts Right to Repair ballot initiative]]
	*[[General Motors data ~~theft~~]]		*[[General Motors data collection and sharing controversy]]

	==References==		==References==
	<references />		<references />
	~~''Note: This article represents an ongoing situation and may be updated as more information becomes available.''~~
	<!-- commenting out to granular categories for the moment -->		<!-- commenting out to granular categories for the moment -->
	[[Category:Data breaches]]		[[Category:Data breaches]]