Skip to Content
Platform.Ontology

Saved passwords and autofill data

Pages cannot read passwords or addresses saved in the browser.

Blocked for appsDevice detailsBrowser stateWeb browsersWhen the page loadsWhile you use it

In one line

Can't see passwords or addresses saved in your browser

Pages cannot read passwords or addresses saved in the browser.

Password managers fill on user action or after an autofill choice. Known weak spot: hidden-field autofill attacks and the :autofill CSS pseudo-class, which reveals that a field was autofilled (a boolean), but never the value before user action.

What it can and can't do

What the user does: You tap a field and choose a saved login or address to fill

It can

  • Tell that a field was filled, using the autofill style check
  • Receive the value you choose to fill in
  • Ask the browser to offer a saved login

It cannot

  • See saved passwords
  • See saved addresses or cards before you choose
  • Get hidden fields filled before you choose, in most browsers
  • See which entries exist in your password manager

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APInone
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: :autofill pseudo-classstringNonestyling hook shows a field was autofilledNot listed
proxy: Credential Management get()stringNonemediated by a prompt for stored credentials of that origin onlyNot listed

Technical limits

  • Credential theft

The story

What it is

Pages cannot read passwords or addresses saved in your browser.

For you

A site cannot ask your browser for a list of your saved passwords. Your browser fills in a login only when you tap or confirm. A site just sees the filled field after that.

For makers

Passwords and addresses are the most valuable data. Browsers fill only after a user action. There are some tricks, like hidden form fields that catch autofill, which vendors keep closing.

Where you see it

TypeExampleApps
bankingA bank login page shows your saved login only when you tap the field and confirm.None named
shoppingA checkout page shows saved addresses after you pick one from the browser prompt.None named
securityA malicious page used hidden form fields to catch autofill data, which browsers now block.None named
socialA social site wanted all saved passwords to catch reuse and cannot.None named
paymentsA payment form shows a saved card after you approve it.Stripe
developerA developer builds login forms that work well with autofill.None named
enterpriseA company portal wanted to see which sites use weak passwords and cannot.None named

Risks

  • Hidden form autofill tricks
  • Autofill after you tap shows data to the page

What the platform says

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Hidden autofill harvesting phishing

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page